Page History
...
In the following example:
- The default "dc" prefix has been redefined as a default "item" prefix used to explicitly apply to all "Items" in the repository.
- A new "Profile" has been defined with its own namespace to be allowed on Collections A and B.
- Each custom "Profile" can be applied to a specific DSO type via an "Applies To" mapping to objects that are of its type
- Each custom "Profile" can enabled in a specific Container (Community, Collection, Item) via an "Allowed In" mapping,
| ID | Namespace | Name | |
|---|---|---|---|
| 1 | dc | ||
| 2 | http://purl.org/dc/terms | dcterms |
Metadata Schema: "dcterms"
where "dcterms:xxx" refinements point to a new Schema in the repository that contains the fields required for the typical dcterms namespace. In the current case, with the "item" and "item2" schema, this schema is not applied directly to Items, but inherited into defined "item" fields through "refinement".
| ID | Field | refines | encoding | default | required | Scope Note |
|---|---|---|---|---|---|---|
| 15 | dcterms.date | rdf:Property | W3CDTF | ${now} | true | Date of publication or distribution. |
| 25 | dcterms.identifier | rdf:Property | URI | true | Uniform Resource Identifier | |
| 37 | dcterms.language | rdf:Property | RFC5646 | en | Catch-all for non-ISO forms of the language of the item, accommodating harvested values. | |
| 40 | dcterms.relation | rdf:Property | URI | Catch-all for references to other related items. | ||
| 57 | dcterms.subject | rdf:Property | Literal | Uncontrolled index term. | ||
| 64 | dcterms.title | rdf:Property | Literal | true | Title statement/title proper. | |
| 66 | dcterms.type | rdf:Property | Class | Nature or genre of content. | ||
| ... | ... | ... | ... | ... | ... | ... |
Metadata Profile Registry
| ID | Namespace | Name | Applies To | Allowed In | |
|---|---|---|---|---|---|
| 1 | item | Item | All Collections | ||
| 2 | http://mydspace/schema/item2 | item2 | Item | Collection A, Collection B |
Item Metadata Profile
:"
itemA"
The following exemplifies how the view over the DSpace Metadata Field Registry would change after these adjustments:
| IDelement | field | refines | encoding | default | required | Scope Note |
|---|---|---|---|---|---|---|
| 15 | issued | dcterms:dateissued | W3CDTF | ${now} | true | Date of publication or distribution. |
| 10 | date | dcterms:date | W3CDTF | ${now} | Use qualified form if possible.25 | |
| uri | dcterms:identifier | URI | true | Uniform Resource Identifier17 | ||
| identifier | dcterms:identifier | Literal | Catch-all for unambiguous identifiers not defined by qualified form; use identifier.other for a known identifier common to a local collection instead of unqualified form.38 | |||
| iso | dcterms:language | RFC5646 | en | Current ISO standard for language of intellectual content, including country codes (e.g. "en_US").37 | ||
| language | dcterms:language | RFC5646 | en | Catch-all for non-ISO forms of the language of the item, accommodating harvested values.44 | ||
| haspart | dcterms:relation | URI | References physically or logically contained item. | |||
| 40 | relation | dcterms:relation | URI | Catch-all for references to other related items.62 | ||
| mesh | dcterms:subject | URI | MEdical Subject Headings63 | |||
| other | dcterms:subject | Literal | Local controlled vocabulary; global vocabularies will receive specific qualifier. | |||
| 57 | subject | dcterms:subject | Literal | Uncontrolled index term. | ||
| 65 | alternative | dcterms:title | Literal | Varying (or substitute) form of title proper appearing in item, e.g. abbreviation or translation | ||
| 64 | title | dcterms:title | Literal | true | Title statement/title proper. | |
| 66 | type | dcterms:type | Class | Nature or genre of content. | ||
| ... | ... | ... | ... | ... | ... | ... |
Item Metadata Profile "B"
The second Item schema types would be expressed as follows:
ID| Field | refines | encoding | default | required | Scope Note | 15||
|---|---|---|---|---|---|---|---|
| item2.date.issued | dcterms:date | W3CDTF | ${now} | true | Date of publication or distribution. | ||
| 25 | item2.identifier.uri | dcterms:identifier | URI | true | Uniform Resource Identifier37 | ||
| item2.language | dcterms:language | RFC5646 | en | Catch-all for non-ISO forms of the language of the item, accommodating harvested values.62 | |||
| item2.subject.mesh | dcterms:subject | URI | MEdical Subject Headings | ||||
| title | 64 | item2.title | dcterms:title | Literal | true | Title statement/title proper.66 | |
| item2.type | dcterms:type | Class | Nature or genre of content. | ||||
| ... | ... | ... | ... | ... | ... | ... |
Metadata Schema: "dcterms"
where "dcterms:xxx" refinements point to a new Schema in the repository that contains the fields required for the typical dcterms namespace. In the current case, with the "item" and "item2" schema, this schema is not applied directly to Items, but inherited into defined "item" fields through "refinement".
Steps To getting There
- Curent default schema should become an "Item Profile"
- New DC and DCTerms Schema should be added to Registry after it has been extended.
- "Item Profile" should have subproperties mapped to DC and DCTERMS schema.
Summary
The above proposal clarifies that new capabilities may emerge for "Typing" , "Restriction" and "Validation" of DSpace objects through extension of the existing data model. The proposed strategy will support stronger typing of not only DSpaceObejcts, but also the values of metadata fields through validation rules such as syntax or vocabulary encodings, requiredness, Dublin Core or other metadata schema types. DSpace should be able to utilize the new MetadataSchema registry as a means to replace large portions of the functionally found in the input-forms.xml file. Additi
...
Overview
Content Tools