The below URL is the starting point for entry of results,
The final part of the URL corresponds collection in the underlying eXist XMLDB. Results are entered into collections such as rezdb:/db/hfagc/d0/d0thomas/ [1].
Create test OR learning entries only within rezdb:/db/test/ using the guest identity.
Warning
Restrict test OR dummy entries to rezdb:/db/test/ keeping rezdb:/db/hfagc/
Use the sidebar quick links to get to your home directory. In order to edit you will need to enter credentials. The rezdb webapp has a separate login account to SVN/Trac although passwords may start out the same.
Although not strictly necessary, it is a good idea to name resources(ie “files” in the XMLDB) corresponding to each reference in a systematic manner as Gigi has done rezdb:/db/hfagc/babar/gigi/
| [1] | Note that rezdb directory URLs require the trailing slash, omitting it gives cocoon errors No pipeline matched request: rezdb/db/hfagc eg rezdb:/db/hfagc |
| [2] | Although eXist supports users belonging to more than one group rezdb does not |
The rezdb web interface provides a delete button if you have the permissions for a collection. However this should not be used for established entries that have already been registered with the system. Note that you cannot delete a resource which you are currently previewing, you need to enter the name of the resource you wish to delete while viewing a collection or another resource.
Instead of deletion, entries should be flagged as inactive using the Edit Header form to prevent all quotes within a result from appearing in reports. Individual quotes can also be flagged as inactive using the Edit Quote form. A header status of inactive takes precedence over individual quote status.
Considerations for problematic modes:
If the mode cannot be encoded using currently defined glyphs then it is straightforward to declare more extras in trunk:images/tex2pdfpng/extras.pl and these code can be used immediately in the rezdb interface, although their previews will be broken (appearing as missing link question marks) until new previews are created and propagated to the editing machine.
This breakage is not important however as long as the agreed upon codes are appropriately in place in the XML.
To add a new particle glyph, add code and corresponding latex to the perl hash datastructure in
Such additions should be coordinated with the heprez administrator, as it some actions are required to create the PDG/PNG/SVG from the latex snippets are re-create indices.
Be careful to choose codes that do not overlap with existing extra or standard codes, and follow the convention of negating to get the conjugate.