DAIS - Digital Archive of the Serbian Academy of Sciences and Arts: Metadata: Difference between revisions
Line 43: | Line 43: | ||
'''Guidance''': | '''Guidance''': | ||
* The order of the authors in the repository should follow their order in the publication. | * The order of the authors in the repository should follow their order in the publication. | ||
* Make a distinction between the authors and contributors! | |||
* Author names are preferably entered using the language and the alphabet of the publication. | * Author names are preferably entered using the language and the alphabet of the publication. | ||
* Upon deposition, a unique alphanumerical string is assigned to each author. In case the author does not have an ORCID profile, all occurrences of the name in the repository should be assigned the same alphanumerical string using [[Ellena]]. In case an author has an ORCID profile, the random string should be replaced in Ellena with the ORCID iD in the format orcid::xxx-xxxx-xxxx-xxxx. Using the Look up feature (choosing names from the list of names already available in the repository) is recommended during the input phase. | * Upon deposition, a unique alphanumerical string is assigned to each author. In case the author does not have an ORCID profile, all occurrences of the name in the repository should be assigned the same alphanumerical string using [[Ellena]]. In case an author has an ORCID profile, the random string should be replaced in Ellena with the ORCID iD in the format orcid::xxx-xxxx-xxxx-xxxx. Using the Look up feature (choosing names from the list of names already available in the repository) is recommended during the input phase. | ||
Line 60: | Line 61: | ||
| Publication date || The date when the item was published/issued | | Publication date || The date when the item was published/issued | ||
'''Guidance:''' | '''Guidance:''' | ||
Preferred format: YYYY. This is a sort field in APP. | 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 | || mandatory, non-repeatable || dc.date.issued | ||
|- | |- | ||
| Volume/issue, pagination || For journal articles and contributions to periodical | | Volume/issue, pagination || For journal articles and contributions to periodical | ||
'''Guidance:''' | '''Guidance:''' | ||
Preferably, digits only. Do not use brackets or abbreviations such as "pp", "str.", etc. | * Preferably, digits only. | ||
* Do not use brackets or abbreviations such as "pp", "str.", etc. | |||
* The volume of a multi-volume book should not be indicated in dc.citation.volume. It should be integrated in the title of the work. | |||
|| mandatory if applicable, repeatable || | || mandatory if applicable, repeatable || | ||
* dc.citation.volume | * dc.citation.volume | ||
Line 77: | Line 80: | ||
* ISBN is acceptable both with and without dashes. | * ISBN is acceptable both with and without dashes. | ||
* Required format for ISSN: "XXXX-XXXX" | * Required format for ISSN: "XXXX-XXXX" | ||
* URIs may change. If a DOI or other PID is available, URI is not necessary. | |||
|| mandatory if applicable, repeatable || | || mandatory if applicable, repeatable || | ||
* dc.identifier.doi | * dc.identifier.doi | ||
Line 89: | Line 93: | ||
| Funding information || Sponsors and funding that supported the work behind the submission. | | Funding information || Sponsors and funding that supported the work behind the submission. | ||
'''Guidance:''' | '''Guidance:''' | ||
* This information is normally stored as a structured string in line with OpenAIRE semantics. | * This information is normally stored as a structured string in line with [https://guidelines.openaire.eu/en/latest/literature/field_projectid.html OpenAIRE semantics]. | ||
* Use this [https://trapist.rcub.bg.ac.rs/Files/projectData.xml list] to find relevant | * Use this [https://trapist.rcub.bg.ac.rs/Files/projectData.xml list] to find relevant strings; copy the content of the tag project relation (between quotation marks) from the list and paste it into the field. The list covers all FP7, Horizon 2020 and Horizon Europe projects in which institutions from Serbia are represented, institutional funding by the Ministry of Education, Science and Technological Development of the (MESTD), projects funded by MESTD (2006–2010, 2011–2019), and the projects funded by the Fund for Science of the Republic of Serbia. | ||
* If a relevant string cannot be found in the list, enter the funding information as free text. | * If a relevant string cannot be found in the list, enter the funding information as free text. | ||
|| mandatory if applicable, repeatable || dc.relation | || mandatory if applicable, repeatable || dc.relation | ||
Line 96: | Line 100: | ||
| Content language || Language of the resource. | | Content language || Language of the resource. | ||
'''Guidance:''' | '''Guidance:''' | ||
Select a language from the drop-down list. Multiple languages may be selected, if necessary. | * Select a language from the drop-down list. Multiple languages may be selected, if necessary. | ||
* This field indicates the language of the content, not of the matadata. | |||
|| mandatory, repeatable, controlled || dc.language | || mandatory, repeatable, controlled || dc.language | ||
|- | |- | ||
| Content type || Type of the resource | | Content type || Type of the resource | ||
'''Guidance:''' | '''Guidance:''' | ||
* Select a value from the drop-down list. The values in the list are based on the [https://guidelines.openaire.eu/en/latest/literature/field_publicationtype.html OpenAIRE | * Select a value from the drop-down list. The values in the list are based on the [https://guidelines.openaire.eu/en/latest/literature/field_publicationtype.html OpenAIRE's info:eu-repo-publication-type-terms vocabulary] expanded to include the main concepts from the [https://vocabularies.coar-repositories.org/documentation/resource_types/ COAR Resource Type vocabulary]. | ||
* If you cannot find the value that accurately describes the content, use "other" and provide additional information in the Note field. | * If you cannot find the value that accurately describes the content, use "other" and provide additional information in the Note field. | ||
|| mandatory, non-repeatable, controlled || dc.type | || mandatory, non-repeatable, controlled || dc.type | ||
Line 107: | Line 112: | ||
| Content version || Version of the resource (draft, submitted, accepted, published, corrected) | | Content version || Version of the resource (draft, submitted, accepted, published, corrected) | ||
'''Guidance:''' | '''Guidance:''' | ||
* Select a value from the drop-down list. The values are in line with the [https://guidelines.openaire.eu/en/latest/literature/field_publicationversion.html | * Select a value from the drop-down list. The values are in line with the [https://guidelines.openaire.eu/en/latest/literature/field_publicationversion.html DRIVER-version info:eu-repo version terms. vocabulary]. | ||
|| mandatory, non-repeatable, controlled || dc.type.version | || mandatory, non-repeatable, controlled || dc.type.version | ||
|- | |- | ||
| Description || Description of the resource | | Description || Description of the resource | ||
'''Guidance:''' | '''Guidance:''' | ||
* | * Although DSpace searches not only the metadata, but also the text extracted from beatstreams (if available), it is highly recommended to provide a description of the resource and its content. | ||
* It is recommended to provide at least a brief description in English. | * It is recommended to provide at least a brief description in English, as this imporoves the discoverability of the content in international aggregators and search engines. | ||
* Descriptions are particularly important for non-publication types of content! | |||
|| recommended, repeatable || dc.description.abstract | || recommended, repeatable || dc.description.abstract | ||
|- | |- | ||
Line 119: | Line 125: | ||
'''Guidance:''' | '''Guidance:''' | ||
* May be submitted in any language and alphabet. | * May be submitted in any language and alphabet. | ||
* It is recommended to provide basic keywords in English as well. | * It is recommended to provide basic keywords in English as well, as this imporoves the discoverability of the content. | ||
* Keywords are particularly important for non-publication types of content! | |||
* Subject controlled vocabularies are currently not implemented in the repository but users are encouraged to define keywords relying on controlled vocabulariies relevant for their discipline. | |||
|| recommended, repeatable || dc.subject | || recommended, repeatable || dc.subject | ||
|- | |- | ||
Line 138: | Line 146: | ||
| Access level || The access to the resouurce in the repository | | Access level || The access to the resouurce in the repository | ||
'''Guidance:''' | '''Guidance:''' | ||
* Select a value from the drop-down list. The terms in the list are in line with the | * Select a value from the drop-down list. The terms in the list are in line with the [https://guidelines.openaire.eu/en/latest/literature/field_accesslevel.html info:eu-repo-Access-Terms vocabulary]. | ||
|| mandatory, non-repeatable || dc.rights | || mandatory, non-repeatable || dc.rights | ||
|- | |- |
Revision as of 00:54, 3 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
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. | 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. In case there is no embargo, this date will be automatically generated and will be the same as the Accession date. | 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 | mandatory, non-repeatable | dc.date.accessioned |
URI | Permanent URL to the item landing 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 |
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. | 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. | 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. | recommended, repeatable | dc.relation.ispartof |
Metadata created automatically upon item publication
Field | Description | Status | DC mapping |
---|---|---|---|
Accession date | The date when the items is accessioned in the repository | mandatory, non-repeatable | dc.date.accessioned |
URI | Permanent URL to the item landing 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 |
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. | 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. | 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. | recommended, repeatable | dc.relation.ispartof |