Difference between revisions of "Temple"

(Created page with "==Editing template and templateAssociation== When opening a template, the corresponding templateAssociation is automatically retrieved. If it does not exist, it is created in ...")
 
(Editing template and templateAssociation)
Line 1: Line 1:
 +
==Starting Temple==
 +
Temple may be opened from the template viewer in ART, with the 'Temple' button, or directly. In the latter case, an editor with just some boilerplate template in it is opened. If opened from ART, the template being viewed is opened. Temple is not an Orbeon XForms application, but eXist + HTML. This means that you need to be logged in to eXist to use Temple. Temple (or more correctly, your browser) may ask credentials when opening Temple.
 +
 
==Editing template and templateAssociation==
 
==Editing template and templateAssociation==
 
When opening a template, the corresponding templateAssociation is automatically retrieved. If it does not exist, it is created in Temple (though not saved yet). The attributes @templateId and @effectiveDate are not shown on templateAssociation. On saving, Temple will copy them from the template. (If you add them manually, they will be overwritten on save.)
 
When opening a template, the corresponding templateAssociation is automatically retrieved. If it does not exist, it is created in Temple (though not saved yet). The attributes @templateId and @effectiveDate are not shown on templateAssociation. On saving, Temple will copy them from the template. (If you add them manually, they will be overwritten on save.)

Revision as of 12:34, 21 January 2014

Starting Temple

Temple may be opened from the template viewer in ART, with the 'Temple' button, or directly. In the latter case, an editor with just some boilerplate template in it is opened. If opened from ART, the template being viewed is opened. Temple is not an Orbeon XForms application, but eXist + HTML. This means that you need to be logged in to eXist to use Temple. Temple (or more correctly, your browser) may ask credentials when opening Temple.

Editing template and templateAssociation

When opening a template, the corresponding templateAssociation is automatically retrieved. If it does not exist, it is created in Temple (though not saved yet). The attributes @templateId and @effectiveDate are not shown on templateAssociation. On saving, Temple will copy them from the template. (If you add them manually, they will be overwritten on save.)

If you need a new template/@id, simply type in 'new', and Temple will create a legal template/@id when saving:

<template id="new"

You can (manually) enter a new @effectiveDate, or choose from the drop-down. In the drop-down, 'now' translates to the time Temple was opened (i.e. "2014-01-21T13:16:08") and 'today' translates to the start of today (i.e. "2014-01-21T00:00:00").

The following rules apply when saving a template:

  • If @id and @effectiveDate exist, template and templateAssociation are overwritten.
  • If @id exists, and @effectiveDate not, a new template is created (in effect, a new version of the template).
  • If @id = 'new', a new template is created. An @effectiveDate must be supplied by the user.
  • If templateAssociation does not exist, it is created (maybe empty, if no concepts are provided).