Faces Application Profile Collection
Jump to navigation
Jump to search
|
Introduction[edit]
Please enter all comments concerning the use cases on the discussion page.
Aim and Scope[edit]
With collection, the whole FACES Data is meant. So currently, only one collection is available. But when the FACES software will be used for further data (e.g. from the Biochemie in Martinsried), a second collection will be exist and the metadata about the collection is relevant.
Technically, a Collection is a container (similar to an album).
The difference between a collection and an album is that a collection must have a date created and an album can have contributors.
Data model[edit]
Namespaces[edit]
| Term URI | http://purl.org/dc/terms/ |
| Name | dcterms: |
| Label | Dublin Core terms |
| Term URI | http://purl.org/escidoc/metadata/terms/0.1/ |
| Name | escidoc: |
| Label | eSciDoc terms |
Syntax Encoding Scheme[edit]
| String data type definition | |
| Name | <string> |
| Label | Character string |
| Definition | A string of ASCII characters. No formatting tags may be included. The following characters must be encoded for XML: '&' - '&'; '<' - '<'; '>' - '>'. A limited list of non-ASCII characters may be included encoded as character entities. |
Describing a Collection[edit]
Title[edit]
| Term URI | http://purl.org/dc/terms/title |
| Name | title |
| Label | Title |
| Defined by: | - |
| DC Definition | A name given to the resource. |
| DC Comment | - |
| eSciDoc Definition | The name of a collection. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Mandatory |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 1; Max: 1; |
| Best practice | - |
| Remarks | Related to "title" from ESciDoc Publication |
Description[edit]
| Term URI | http://purl.org/dc/terms/abstract |
| Name | abstract |
| Label | Abstract |
| Defined by: | - |
| DC Definition | A summary of the resource. |
| DC Comment | - |
| eSciDoc Definition | A short description of a collection. |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Mandatory |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 1; Max: 1; |
| Best practice | - |
| Remarks | Related to "abstract" fromESciDoc Publication |
Creator[edit]
| Term URI | http://purl.org/dc/terms/creator |
| Name | creator |
| Label | Creator |
| Defined by: | - |
| DC Definition | An entity primarily responsible for making the resource. |
| DC Comment | Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity. |
| eSciDoc Definition | The creator of a collection. |
| eSciDoc Comment | For Faces, only organizations are valid creators. |
| Type of term | Property |
| Refines | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | |
| Obligation | Mandatory |
| Condition | - |
| Datatype | string |
| Occurrence | Min: 1; Max: Unbounded; |
| Best practice | - |
| Remarks | Related to "creator" from ESciDoc Publication |
Created[edit]
| Term URI | http://purl.org/dc/terms/created |
| Name | created |
| Label | Date Created |
| Defined by: | - |
| DC Definition | Date of creation of the resource. |
| DC Comment | - |
| eSciDoc Definition | Date of creation of the collection (not the online creation but the creation of the pictures and its data). |
| eSciDoc Comment | - |
| Type of term | Property |
| Refines | - |
| Refined by | - |
| Encoding Scheme For | - |
| Has Encoding Scheme | - |
| Obligation | Mandatory |
| Condition | - |
| Datatype | date |
| Occurrence | Min: 1; Max: 2; |
| Best practice | - |
| Remarks | As it normally takes a lot of time to create a collection, the date can also be entered as a period (from - till). Related to "created" from ESciDoc Publication |
Related Application Profiles[edit]
eSciDoc
Faces