...
Moreover, in the dLibra system, there is a set of roles which can be assigned to attributes. Those roles have semantic meaning, that is, they tell the system that the given attribute plays a specific role in the system. For example, when there is the “Title” attribute in the system, the system does not know that it is a basic designation of an element which should constitute the default name of the element. It is only after the “Title” role has been assigned to the “Title” attribute that the system knows that the “Title” attribute has the “Title” role.
The
...
Meaning of
...
Descriptive Metadata of
...
Objects
The
...
Descriptive Metadata of an Edition
The descriptive metadata created for a release edition describe the content of that releaseedition. The metadata are displayed to users of the web pages of the library when they browse the properties of a publication release edition and the content of that releaseedition.
Planned Publication Descriptive Metadata
Planned publication descriptive metadata are the descriptive metadata of the first releaseedition, which will be created when content is added to a given planned publication. Thus, when a planned publication is transformed into a standard publication (that is, when content is added to it), the dLibra system automatically transfers the descriptive metadata of the planned publication to the first release edition of the standard publication which is being created. Thanks to that, the users of the library web pages who browse planned publications can see the complete description of the digital object (standard publication) which will, in the future, replace the planned publication.
...
Group publication metadata have two meanings. First, they describe the given group publication. Second, they are inherited by all publications in the described group publication. That is very important when subsequent digital objects are entered to that group publication. If a group publication is described with metadata shared by all objects in that publication, the editors will not have to enter those metadata for every object in that group publication, and they will be able to focus on entering the descriptions specific to particular objects.
For example, for a group publication called Daily, the editors can enter attribute value Publisher to its metadata. Then, all publications in the Daily group publication will inherit that value, so the editors will not have to enter it for publications later added to the Daily group publication.
...
Directory Descriptive Metadata
Catalog Directory descriptive metadata have special meaning because catalogs directories are only visible in the Editor and Administrator Application (they are not visible for web page users). When metadata are entered in a catalogdirectory, then all metadata ascribed to that catalog that directory will be, by default, entered in the creator of all elements created in that catalogdirectory, on the page for entering descriptive metadata. That mechanism makes it possible to specify the description which will be proposed by default for all elements created in that catalogdirectory. For example, if in the given catalogdirectory, publications are created by only one institution, which has permissions for all objects entered in that catalogdirectory, the attribute value can be “Permissions”.
Methods of Entering Metadata
...