Page History

...

A DSpace installation running Manakin may have several Themes associated with it. When applied to a page, a Theme determines most of the pageíspage's look and feel. Different themes can be applied to different sets of DSpace pages allowing for both variety of styles between sets of pages and consistency within those sets. The xmlui.xconf configuration file determines which Themes are applied to which DSpace pages (see the Chapter 7. Manakin \[XMLUI\] Configuration and Customization for more information on installing and configuring themes). Themes may be configured to apply to all pages of specific type, like browse-by-title, to all pages of a one particular community or collection or sets of communities and collections, and to any mix of the two. They can also be configured to apply to a singe arbitrary page or handle.

...

Many elements in the DRI system (all top-level containers, character classes, and many others) contain one or several of the three standard attributes: id, n, and rend. The id and n attributes can be required or optional based on the elementís element's purpose, while the rend attribute is always optional. The first two are used for identification purposes, while the third is used as a display hint issued to the styling step.

...

The name attribute n is simply the name assigned to the element, and it is used to distinguish an element from its immediate peers. In the example of a particular list, all items in that list will have different names to distinguish them from each other. Other lists in the document, however, can also contain items whose names will be different from each other, but identical to those in the first list. The n attribute of an element is therefore unique only in the scope of that elementís element's parent and is used mostly for sorting purposes and special rendering of a certain class of elements, like, for example, all first items in lists, or all items named "browse". The n attribute follows the same rules as id when determining whether or not it is required for a given element.

...

Merging the options elements is somewhat different. First, list elements under options of both documents are compared with each other. Those unique to either document are simply added under the new options element, just like divs under body. In case of duplicates, that is list elements that belong to both documents and have the same n attribute, the two lists will be merged into one. The new list element will consist of the main documentís document's head element, followed label-item pairs from the main document, and then finally the label-item pairs of the feeder, provided they are different from those of the main.

...

The cell element contained in a row of a table carries content for that table. It is a character container, just like p, item, and hi, and its primary purpose is to display textual data, possibly enhanced with hyperlinks, emphasized blocks of text, images and form fields. Every cell can be annotated with a role (the most common being ìheaderî and ìdataî"header" and "data") and can stretch across any number of rows and columns. Since cells cannot exist outside their container, row, their id attribute is optional.

...

• cols: (optional) The number of columns the cell spans.
• id: (optional) A unique identifier of the element.
• n: (optional) A local identifier used to differentiate the element from its siblings.
• rend: (optional) A rendering hint used to override the default display of the element.
• role: (optional) An optional attribute to override the containing row√≠s row's role settings.
• rows: (optional) The number of rows the cell spans.

...

The instance element contains the value associated with a form fieldís field's multiple instances. Fields encoded as an instance should also include the values of each instance as a hidden field. The hidden field should be appended with the index number for the instance. Thus if the field is "firstName" each instance would be named "firstName_1", "firstName_2", "firstName_3", etc...

...

• cols: (optional) The default number of columns that the text area should span. This applies only to textarea field types.
• maxlength: (optional) The maximum length that the theme should accept for form input. This applies to text and password field types.
• multiple: (optional) yes/no value. Determine if the field can accept multiple values for the field. This applies only to select lists.
• operations: (optional) The possible operations that may be preformed on this field. The possible values are "add" and/or "delete". If both operations are possible then they should be provided as a space separated list.The "add" operations indicates that there may be multiple values for this field and the user may add to the set one at a time. The front-end should render a button that enables the user to add more fields to the set. The button must be named the field name appended with the string "_add", thus if the field's name is "firstName" the button must be called "firstName_add".The "delete" operation indicates that there may be multiple values for this field each of which may be removed from the set. The front-end should render a checkbox by each field value, except for the first, The checkbox must be named the field name appended with the string "_selected", thus if the field's name is "firstName" the checkbox must be called "firstName_selected" and the value of each successive checkbox should be the field name. The front-end must also render a delete button. The delete button name must be the field√≠s field's name appended with the string "_delete".
• rows: (optional) The default number of rows that the text area should span. This applies only to textarea field types.
• size: (optional) The default size for a field. This applies to text, password, and select field types.

...

The repository element is used to describe the repository. Its principal component is a set of structural metadata that carrier information on how the repositoryís repository's objects under objectMeta are related to each other. The principal method of encoding these relationships at the time of this writing is a METS document, although other formats, like RDF, may be employed in the future.

Parent

• repositoryMeta

Children

• none

Attributes

• repositoryID: requiredA unique identifier assigned to a repository. It is referenced by the object element to signify the repository that assigned its identifier.
• url: requiredA url to the external METS metadata file for the repository.

  Code Block
  <repositoryMeta> <repository repositoryID="123456789" url="/metadata/handle/1234/4/mets.xml" /> </repositoryMeta>

...

The trail element carries information about the userís user's current location in the system relative of the repositoryís repository's root page. Each instance of the element serves as one link in the path from the root to the current page.

...

• identifier (suggested): A unique identifier associated with the user.
• identifier.email (suggested): The requesting user√≠s user's email address.
• identifier.firstName (suggested): The requesting user√≠s user's first name.
• identifier.lastName (suggested): The requesting user√≠s user's last name.
• identifier.logoutURL (suggested): The URL that a user will be taken to when logging out.
• identifier.url (suggested): A url reference to the user√≠s user's page within the repository.
• language.RFC3066 (suggested): The requesting user√≠s user's preferred language selection code as describe by RFC3066
• rights.accessRights (required): Determines the scope of actions that a user can perform in the system. Accepted values are:
  • none: The user is either not authenticated or does not have a valid account on the system
  • user: The user is authenticated and has a valid account on the system
  • admin: The user is authenticated and belongs to the system√≠s system's administrative group
    See the metadata tag entry for more information on the structure of metadata elements.

...

The xref element is a reference to an external document. It can be mixed freely with text, and any text within the tag itself will be used as part of the linkís link's visual body.

Parent

cell

p

item

...