Faces Application Profile Album
|
Introduction[edit]
Please enter all comments concerning the use cases on the discussion page.
Aim and Scope[edit]
NOTE: Albums have been called Study Sets or - technically - Bundles before.
An album is a set of selected pictures, which can be published (state released) but also can be used as a private (state submitted) selection. It can be created by a user who automatically is the owner of the album. To create an album means to create new content with its own metadata set.
Albums will be versioned. This means after each change of the album a new version will be created.
As being a content that can be published, each album in its internal workflow goes through the following states: submitted (private), released (published) and (optionally) withdrawn. When changing the status, a version comment can be entered and will be stored. The main workflow is the following:
- An album is created by the owner and is visible by default only to him (status: submitted). In this state, the owner can also decide to open the album for further editing and specifies users who can further work on the album.
- After decision that the album is in state for publishing, the owner publishes the album and it will be assigned with a persistent identifier. Released albums are visible to all account users and can be referenced as source for a publication. They can be cited, because the metadata of the album will be available for all users (not only account users, as the pictures will be). This information will also be part of the application release agreement. (status: released).
- Optionally: An album can be withdrawn by the owner in case when it is not a valid scientific content any more (or from other reasons). Withdrawn albums are only visible through the owners album list or through the direct URL (status: withdrawn).
Technically, an album is a container (similar to a collection).
The difference between an album and a collection is that an album can have contributors and a collection must have a date created.
Data model[edit]
Namespaces[edit]
Term URI | http://purl.org/dc/terms/ |
Name | dcterms: |
Label | Dublin Core 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 an Album[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 an album. |
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 | - |
Remakrs | Related to "title" form ESciDoc Publication |
Description[edit]
Term URI | http://purl.org/dc/terms/description |
Name | description |
Label | Description |
Defined by: | - |
DC Definition | - |
DC Comment | - |
eSciDoc Definition | A short description of an album. |
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 | - |
Remakrs | Related to "abstract" from ESciDoc 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 author of an album. |
eSciDoc Comment | For Faces, only persons are valid creators. |
Type of term | Property |
Refines | - |
Refined by | - |
Encoding Scheme For | - |
Has Encoding Scheme | - |
Obligation | Mandatory |
Condition | - |
Datatype | string |
Occurrence | Min: 1; Max: Unbounded; |
Best practice | - |
Remakrs | The first creator is always the owner of the item.
Related to "creator" from ESciDoc Publication |
Organization[edit]
Term URI | http://www.w3.org/2006/vcard/ns/org |
Name | org |
Label | Organization |
Defined by: | - |
vCard Definition | An organization associated with a person. |
vCard Comment | - |
eSciDoc Definition | The organizational unit the person was affiliated to when creating the album. |
eSciDoc Comment | - |
Type of term | Property |
Refines | - |
Refined by | - |
Encoding Scheme For | - |
Has Encoding Scheme | - |
Obligation | Mandatory |
Condition | The domain of the vCard:org property is the vCard:VCard class. The range of the v:org property is the v:Organization class. |
Datatype | string |
Occurrence | Min: 1; Max: unbounded; |
Best practice | - |
Remarks | - |
Contributor[edit]
Term URI | http://purl.org/dc/terms/contributor |
Name | contributor |
Label | Contributor |
Defined by: | - |
eSciDoc Definition | The editor/contributor of an album .One or more account users who have the rights to edit an album. |
eSciDoc Comment | Only Contributers from the type Editor are allowed. |
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 | - |
Remakrs | Related to "contributor" from ESciDoc Publication |
Related Application Profiles[edit]
eSciDoc
Faces