Differences between revisions 5 and 6
Revision 5 as of 2010-01-04 08:20:13
Size: 1623
Editor: eab
Comment:
Revision 6 as of 2010-03-17 13:09:04
Size: 1626
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
For all entries in the collection there are individual and common metadata, both should be included in the files internal descriptive metadata ~-[:GuidelinesForNewDatamodel: ref: datamodel guidelines]-~. For all entries in the collection there are individual and common metadata, both should be included in the files internal descriptive metadata ~-[[GuidelinesForNewDatamodel| ref: datamodel guidelines]]-~.
Line 32: Line 32:
Consider the [:../Sub_collections: Sub collections] and the [:../FRBR_Relations: FRBR Relations] in order to create a sufficient division of the data. Consider the [[../Sub collections| Sub collections]] and the [[../FRBR Relations| FRBR Relations]] in order to create a sufficient division of the data.

Descriptive metadata

Context

For all entries in the collection there are individual and common metadata, both should be included in the files internal descriptive metadata ref: datamodel guidelines.

The internal descriptive metadata might have a structure that is apparent, it might have some that is not.

Either way it should be considered what to include and what, if anything, to exclude.

It might be a good idea to use the structure in the collection; however this should be considered carefully, the inclusion of structure should not contain any information but only be a tool to ease the work with the collection.

Description of pattern

The division of metadata into sub-groups that will ease the use of the metadata. This division should be in convenient sizes and the groups should contain entries that are coherent.

Problem description

When much data is available it becomes increasingly difficult to maintain a good overview of the data, and a quick peek will not be sufficient to decipher the subjects of the metadata in question.

Solution

Try to section the metadata in a way that maintains it in one data-object.

But maintain a structure that groups meta-data in a way where there is a relationship internally in the grouping of the data.

Consider next

Consider the Sub collections and the FRBR Relations in order to create a sufficient division of the data.

GuidelinesForNewDatamodel/PatternLanguage/Descriptive metadata (last edited 2010-03-17 13:09:04 by localhost)