Difference between revisions of "ViRR Application Profile"
Jump to navigation
Jump to search
m |
|||
| Line 1,125: | Line 1,125: | ||
[[Category:Virtueller Raum Reichsrecht|Application Profile ViRR-Element]] | [[Category:Virtueller Raum Reichsrecht|Application Profile ViRR-Element]] | ||
[[Category:Application_Profiles| | [[Category:Application_Profiles|ViRR Application Profile]] | ||
Revision as of 10:06, 1 December 2008
|
Introduction[edit]
Please enter all comments on the discussion page.
PLEASE NOTE: For ViRR, MODS will be used instead of DC (mapping DC to MODS).
Aim and Scope[edit]
The eSciDoc Application Profile ViRR-Element documents the elements used by the eSciDoc solution ViRR to describe its content entities. Additional information about objects (properties for items and its components) and structural relations between objects are also existing, but currently not considered in the AP.
This eSciDoc Application Profile ViRR-Element will be used for two different elements within ViRR:
- Publication (three different types exist)
- Multivolume (construct for several books who belongs together)
- Volume (part of a multivolume)
- Monograph (stand alone book)
- Structural Element
- The content of one real existing book (volume or monograph) is structured via a table of contents. This detailed ToC for the volume or monograph is created by all structural elements defined.
In the first step, the AP is meant for documenting the existing requirements for the metadata. Later on, the AP shall be transformed to RDF.
Designated community[edit]
Functional requirements[edit]
Data model[edit]
If there is an overall data model. If not, detailed data models can be found at the beginning of each application profile.
Describing a VirrElement[edit]
STILL MISSING:
- The order number of a volume which belongs to a multivolume (e.g. Band 3).
- Would consider naming convention for names i.e. law-type instead of law_type (this is how it is done with application profiles at present i think). -- Natasa
- In the ESciDoc Application Profiles sometimes names are written in one word (lawType), sometimes with underscore (law_type) and sometimes with hyphen (law-type). I think its a good idea to use only one form in all APs. --Kristina 07:56, 20 November 2008 (UTC)
Title[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#title |
| Name | title |
| Label | Title |
| Defined by: | - |
| MODS Definition | A word, phrase, character, or group of characters that constitutes the chief title of a resource (i.e. the title normally used when citing the resource). |
| MODS Comment | - |
| eSciDoc Definition | The title of the resource. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | http://purl.org/dc/terms/alternative |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Optional* |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: 1 |
| Best practice | - |
| Remarks | conforms to dc:title |
| Constraints | *Mandatory for multivolume, volume and monograph. |
AlternativeTitle[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#subtitle |
| Name | alternative |
| Label | Alternative Title |
| Defined by: | - |
| MODS Definition | A word, phrase, character, or group of characters that contains the remainder of the title information after the title proper |
| MODS Comment | - |
| eSciDoc Definition | Alternative titles of the resource, e.g. sub-titles, volume-titles. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Optional |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: Unbounded |
| Best practice | - |
| Remarks | conforms to dcterms:alternative |
| Constraints | - |
Genre[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#genre |
| Name | type |
| Label | Genre |
| Defined by: | - |
| MODS Definition | A term(s) that designates a category characterizing a particular style, form, or content, such as artistic, musical, literary composition, etc. |
| MODS Comment | - |
| eSciDoc Definition | The genre of a resource describes the type of the resource. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | For structural elements: List of structural element types For publications: multivolume (u), volume (n), monograph (m) (based on MAB2 Satzarten) |
| Obligation | Mandatory |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 1; Max: 1; |
| Best practice | - |
| Remarks | - |
| Constraints | - |
Creator[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#name |
| Name | name |
| Label | Creator |
| Defined by: | - |
| MODS Definition | The name of a person, organization, or event (conference, meeting, etc.) associated in some way with the resource. |
| MODS Comment | - |
| eSciDoc Definition | Any person who essentially participated in creating the resource with a specific task. |
| eSciDoc Comment | For ViRR, only persons are valid creators. |
| Type of term | Property |
| Refines | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | http://www.allegro-c.de/doku/form2004/for1e.htm#xtocid408 only following values are needed: |
| Obligation | Optional* |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: Unbounded; |
| Best practice | - |
| Remarks | As there isn't any official translation from the German Allegro Terms to the marc values I translated them by myself. --Kristina 11:43, 15 September 2008 (UTC) |
| Constraints | *Mandatory for multivolume, volume and monograph. |
Creation Place[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#place |
| Name | creation_place |
| Label | Creation Place |
| Defined by: | - |
| MODS Definition | Name of a place associated with the issuing, publication, release, distribution, manufacture, production, or origin of a resource. |
| MODS Comment | - |
| eSciDoc Definition | The place where the described resource has been created (the location of the publisher). |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Optional |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: 1 |
| Best practice | - |
| Remarks | - |
| Constraints | - |
Created[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#datecreated |
| Name | created |
| Label | Date Created |
| Defined by: | - |
| MODS Definition | the date of creation of the resource. |
| MODS Comment | - |
| eSciDoc Definition | The date when the structural element was created. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | http://www.w3.org/TR/NOTE-datetime |
| Obligation | Optional |
| Condition | - |
| Datatype | date |
| Occurrence | Min: 0; Max: 1 |
| Best practice | - |
| Remarks | - |
Subject[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#topic |
| Name | subject |
| Label | Subject |
| Defined by: | - |
| MODS Definition | "topic" is used as the tag for any topical subjects that are not appropriate in the <geographic>, <temporal>, <titleInfo>, or <name> subelements. If there is an uncontrolled term, <topic> is used (since <subject> is a binding element). <topic> is equivalent to MARC 21 fields 650 and 6XX subfields $x and $v (with authority attribute defined) and MARC 21 field 653 with no authority attribute.
Note that form subdivisions in LCSH are coded as <topic> because it was felt that the distinction was too difficult to make. |
| MODS Comment | - |
| eSciDoc Definition | Free keywords describing the resource. |
| eSciDoc Comment | use subject.topic |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Optional |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: Unbounded |
| Best practice | Use a DDC term to classify the resource. |
| Remarks | - |
| Constraints | - |
LawType[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#subject |
| Name | law_type |
| Label | Law Type |
| Defined by: | - |
| MODS Definition | "genre" includes a genre or form used as part of a subject string when the subject authority distinguishes subdivisions of the main subject (e.g. LCSH). If describing the genre of a resource as a whole, use in the <genre> element. This is used to facilitate mapping between subject authorities that use form subdivisions. Equivalent to subfield $v in MARC 21 6XX fields. |
| MODS Comment | - |
| eSciDoc Definition | The type of the described law. |
| eSciDoc Comment | use subject.genre |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | Reichsabschied, Reichsgutachten, Ordnung, Vertrag, Andere (with display of a freetext field) |
| Obligation | Optional |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: 1 |
| Best practice | - |
| Remarks | - |
| Constraints | - |
Legislature[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#subject |
| Name | legislature ("Körperschaft") |
| Label | Legislature |
| Defined by: | - |
| MODS Definition | "name" includes a name used as a subject. All subelements and attributes used under the top-level element <name> may be used. An authority attribute may also be used at this level if desired in addition to at the highest level (under <subject>). Equivalent to MARC 21 fields 600, 610, 611. |
| MODS Comment | - |
| eSciDoc Definition | The legislature of the described law. |
| eSciDoc Comment | use subject.name or subject.affiliation |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Optional |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: 1 |
| Best practice | - |
| Remarks | - |
| Constraints | - |
Description[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#note |
| Name | note |
| Label | Description |
| Defined by: | - |
| DC Definition | An account of the resource. |
| DC Comment | Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. |
| eSciDoc Definition | A field for additional information about the structural element. |
| eSciDoc Comment | Can be used e.g. for external links to other digitizing projects who work with the same material. |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Optional |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: 1 |
| Best practice | - |
| Remarks | - |
Continuation[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#relatedItem |
| Name | continuation |
| Label | Continuation |
| Defined by: | - |
| MODS Definition | Information that identifies other resources related to the one being described. |
| MODS Comment | attribute succeeding |
| eSciDoc Definition | A relation to another structural element within ViRR which is the continuation of the current structural element. |
| eSciDoc Comment | - |
| Type of term | - |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Optional |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: 1; |
| Best practice | Free text field where the user can enter the corresponding multivolume, volume (or monograph) and structural element. |
| Remarks | use attribute succeeding |
Language[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#language |
| Name | language |
| Label | Language |
| Defined by: | - |
| MODS Definition | a designation of the language in which the content of a resource is expressed. |
| MODS Comment | - |
| eSciDoc Definition | The language of the resource. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | RFC 4646 |
| Obligation | Optional |
| Condition | - |
| Datatype | string |
| Occurrence | Min:0; Max: 1 |
| Best practice | - |
| Remarks | conforms to dc:language |
| Constraints | - |
Identifier[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#identifier |
| Name | identifier |
| Label | Identifier |
| Defined by: | - |
| MODS Definition | "identifier" contains a unique standard number or code that distinctively identifies a resource. |
| MODS Comment | - |
| eSciDoc Definition | An internal or external identifier referencing the described resource. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | Signature (of the location), internal id |
| Obligation | Optional |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: Unbounded |
| Best practice | - |
| Remarks | conforms to dc:identifier |
| Constraints | - |
Publisher[edit]
| Term URI | http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html#publisher |
| Name | publisher |
| Label | Publisher |
| Defined by: | - |
| MODS Definition | The name of the entity that published, printed, distributed, released, issued, or produced the resource. |
| MODS Comment | - |
| eSciDoc Definition | The institution (publisher name) which has published the resource. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | http://purl.org/escidoc/metadata/terms/publishinginfo |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Optional |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: 1 |
| Best practice | - |
| Remarks | conforms to dc:publisher |
| Constraints | - |
Issued[edit]
| Term URI | http://purl.org/dc/terms/issued |
| Name | issued |
| Label | Date Issued |
| Defined by: | - |
| DC Definition | Date of formal issuance (e.g., publication) of the resource. |
| DC Comment | - |
| eSciDoc Definition | The date which is associated with the publishing of the resource. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | http://purl.org/dc/terms/date |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | http://www.w3.org/TR/NOTE-datetime |
| Obligation | Optional |
| Condition | - |
| Datatype | date |
| Occurrence | Min: 0; Max: 1* |
| Best practice | - |
| Remarks | Is part of MODS: <dateIssued> |
| Constraints | *Also date ranges (from - until) should be possible (as e.g. for multivolumes). |
Location[edit]
| Term URI | http://purl.org/dc/terms/Location |
| Name | location |
| Label | Location |
| Defined by: | - |
| DC Definition | A spatial region or named place. |
| DC Comment | - |
| eSciDoc Definition | The name of the library where the resource is currently located. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Optional |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: 1 |
| Best practice | - |
| Remarks | - |
| Constraints | - |
TotalNumberOfPages[edit]
| Term URI | http://purl.org/dc/terms/extent |
| Name | extent |
| Label | Total number of pages |
| Defined by: | - |
| DC Definition | The size or duration of the resource. |
| DC Comment | - |
| eSciDoc Definition | The number of pages of the resource. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Optional |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 0; Max: 1 |
| Best practice | - |
| Remarks | Is part of MODS: <physicalDescription> <extend> |
| Constraints | - |
Further data[edit]
Following data will be displayed for each structural element (not for multivolume, volume and monograph), but is not stored in the application profile (as it is already stored in the ToC):
- Start Page
- Mandatory
- Min: 1; Max: 1
- End Page
- Optional
- Min: 0; Max: 1