DAIS - Digital Archive of the Serbian Academy of Sciences and Arts: Metadata: Difference between revisions
No edit summary |
|||
Line 156: | Line 156: | ||
! Field !! Description !! Status !! DC mapping | ! Field !! Description !! Status !! DC mapping | ||
|- | |- | ||
| Accession date || The date when the items is accessioned in the repository || mandatory, non-repeatable || dc.date.accessioned | | Accession date || The date when the items is accessioned in the repository, in the format YYYY-MM-DD || mandatory, non-repeatable || dc.date.accessioned | ||
|- | |- | ||
| URI || Permanent URL to the item landing page || mandatory, non-repeatable || dc.identifier.uri | | URI || Permanent URL to the item landing page. It is displayed as an interactive link on the item page. || mandatory, non-repeatable || dc.identifier.uri | ||
|- | |- | ||
| Resource URL || URL to the resource (bitstream). Created only if the resource is publicly available. || mandatory if applicable, non-repeatable || dc.identifier.fulltext | | Resource URL || URL to the resource (bitstream). Created only if the resource is publicly available in the form of an interactive link opening the bitstream / data file. || mandatory if applicable, non-repeatable || dc.identifier.fulltext | ||
|- | |- | ||
| Handle - persistent identifier || Unique and persistent Handle URL to the item landing page. Created automatically for all deposited items, excepts those that already have a Handle (e.g items imported from another repository using Handles). || mandatory, non-repeatable || dc.identifier.rcub | | Handle - persistent identifier || Unique and persistent Handle URL to the item landing page. Created automatically for all deposited items, excepts those that already have a Handle (e.g items imported from another repository using Handles). || mandatory, non-repeatable || dc.identifier.rcub |
Revision as of 15:11, 11 June 2022
This public wiki is about the DAIS – Digital Archive of the Serbian Academy of Sciences and Arts
See also:
- Mission
- General information
- Organization scheme
- Workflows
- Item lifecycle
- Security
- Preservation plan
- Terms of Service
- Helpdesk
Metadata inserted through the input form
Field | Description | Status | DC mapping |
---|---|---|---|
Title | The main title of the item.
Guidance:
|
mandatory, repeatable | dc.title |
Author | Names of the primary authors of the item in the format surname comma any other name(s).
Guidance:
In case a name in the publication is incorrect, enter the correct form in the repository and make a note in the Note field indicating the error in the publication. |
mandatory if applicable, repeatable | dc.creator |
Contributor | All types of contributors and secondary authors (including editors, translators, etc.)
Guidance: See under Author. The field should contain names only. Do not indicate the role, e.g. "(ed.)" |
mandatory if applicable, repeatable | dc.contributor |
Source and/or provenance | Source publication or collection
Guidance: Provide the title of the source publication or collection (if applicable, for non-publication content types). Follow the guidance for the Title field. If a publication is part of a monographic series, do not use this field for the series title! |
mandatory if applicable, non-repeatable | dc.source |
Publication date | The date when the item was published/issued
Guidance: Preferred format: YYYY. This is a sort field in APP. If relevant, full dates should be provided in dc.date.created) |
mandatory, non-repeatable | dc.date.issued |
Volume/issue, pagination | For journal articles and contributions to periodical
Guidance:
|
mandatory if applicable, repeatable |
|
Identifiers | Various identifiers. DOI, ISBN, ISSN, ISMN should be provided if available. Scopus and the Web of Science identifiers are usually assigned by repository managers through NomadLite
Guidance:
|
mandatory if applicable, repeatable |
|
Funding information | Sponsors and funding that supported the work behind the submission.
Guidance:
|
mandatory if applicable, repeatable | dc.relation |
Content language | Language of the resource.
Guidance:
|
mandatory, repeatable, controlled | dc.language |
Content type | Type of the resource
Guidance:
|
mandatory, non-repeatable, controlled | dc.type |
Content version | Version of the resource (draft, submitted, accepted, published, corrected)
Guidance:
|
mandatory, non-repeatable, controlled | dc.type.version |
Description | Description of the resource
Guidance:
|
recommended, repeatable | dc.description.abstract |
Subject | Free-style keywords.
Guidance:
|
recommended, repeatable | dc.subject |
Publisher | Name of the organization(s) or entities which published the deposited item or were responsible for its production.
Guidance:
|
recommended, repeatable | dc.publisher |
Note | Any annotation or comment
Guidance:
|
optional, repeatable | dc.description.other |
Access level | The access to the resouurce in the repository
Guidance:
|
mandatory, non-repeatable | dc.rights |
License | The license under which the resource (bitstream) is distributed. A Creative Commons license or All rights reserved should be selected from the drop-down list. If required by the Designated Community, other licences may also be supported. There are no technical limitations in this respect.
|
mandatory, non-repeatable | dc.rights.license |
Copyright holder | The name of the person or entity holding the copyright. | optional, repeatable | dc.rights.holder |
Embargo end date | The date when the resource will be automatically made publicly available.
Guidance: In case there is no embargo, this date will be automatically generated and will be the same as the Accession date. In case there is an embargo, the depositor should indicate the embargo end date in the appropriate field (by marking it in the calendar) immediatelly after uploading the file. |
optional, non-repeatable | dc.date.available |
Metadata created automatically upon item publication
Field | Description | Status | DC mapping |
---|---|---|---|
Accession date | The date when the items is accessioned in the repository, in the format YYYY-MM-DD | mandatory, non-repeatable | dc.date.accessioned |
URI | Permanent URL to the item landing page. It is displayed as an interactive link on the item page. | mandatory, non-repeatable | dc.identifier.uri |
Resource URL | URL to the resource (bitstream). Created only if the resource is publicly available in the form of an interactive link opening the bitstream / data file. | mandatory if applicable, non-repeatable | dc.identifier.fulltext |
Handle - persistent identifier | Unique and persistent Handle URL to the item landing page. Created automatically for all deposited items, excepts those that already have a Handle (e.g items imported from another repository using Handles). | mandatory, non-repeatable | dc.identifier.rcub |
Metadata added by repository managers (if applicable)
Field | Description | Status | DC mapping |
---|---|---|---|
Link to a different version of the resource | DOI, other PID or URI of a different version of the resource.
Guidance: This field is used when multiple versions of the same resource are available, e.g. a preprint is published on a preprint server, or both the Version of Record and the Author Accepted Manuscript are deposited in the repository. In the former case, the PID in the form of an interactive link should be pasted in this field. In the latter case, the handle of the other version (in the form of an interactive link) should be provided. |
recommended, repeatable | dc.relation.isversionof |
Link to related materials | DOI, other PID or URI of any supplementary materials, research data related to the resource (e.g. research data related to a published article), errata, etc.
Guidance: This field is used when various types of mutually related materials are available in the repository. To establish links among two records containing such materials, paste the PIDs of the related materials in this fiels. For example, to connect a record containing data related to a publication with the publication record, paste the handle (as an interactive link) of the data record in the field dc.relation.isreferencedby in the publication record, and vice versa. If a publication has a DOI, then both the publication's handle (from the repository) and DOI shpuld be added (the field is repeatable). |
recommended, repeatable | dc.relation.isreferencedby |
Link to a related resource in which the described resource is physically or logically included | DOI, other PID or URI of the related resource.
Guidance: This field is used when e.g. both the book and one or more chapters contained in it are available n the repository. In this case, the handle of the book record should be provided (as an interactive link) in this field. The same applies to any other collection and its parts. |
recommended, repeatable | dc.relation.ispartof |