Info | ||
---|---|---|
| ||
This page contains DSpace-software specific notes in relation to the SHARE Proposal. More general questions/comments on the SHARE Proposal are also available on the page: SHARE Proposal Some of these notes are also borrowed from the OR13 DSpace Developers Meeting, where the SHARE proposal was discussed briefly:
General DSpace-specific comments/questions are made throughout the below summary (in italics) and are marked as such. |
...
- author
- DSpace stores in 'dc.contributor.author' or 'dc.creator'
- article title
- DSpace tends to capture article titles as the 'dc.title'
- journal title
- Currently, DSpace only captures a Journal title as a part of the "dc.identifier.citation" field (which is a human-readable citation)
- This likely would need to be a new metadata field added to DSpace
- abstract
- DSpace captures in 'dc.description.abstract'
- award number
- Would need to be a new metadata field in DSpace. Unclear whether this is a single field, or if we'd also need to store the Agency information (the agency who assigned this number)
- Principal Investigator ID (ORCID or ISNI)
- http://www.isni.org/isni_and_orcid
- Would need to be a new metadata field in DSpace.
- Possible issue: currently, it's not possible to associate related metadata fields in DSpace
- . So, simply storing an ORCID as metadata may be problematic, as it may not be associated with the proper author entry.
- Some additional notes on ORCID + DSpace are at: ORCID Integration
- Unclear if this is just storage of an ORCID, or something beyond that?
- designated repository number
- Perhaps this is just the "site" handle for a DSpace repository? e.g. [handle-prefix]/0 is the Handle / Presistent Identifier for a site (although currently it does not "resolve" via hdl.handle.net)
...
- PI Identifier (Also mentioned in "Requisite Conditions")
- See notes above under "Minimum SHARE metadata fields"
- Award Number (Also mentioned in "Requisite Conditions")
- See notes above under "Minimum SHARE metadata fields"
- Publication ID - "unique, persistent identifier to reference the journal article of the publication"
- For DSpace, this could be the item handle assigned by the repository
- Data Set ID - "resolvable, persistent identifier to location of stored data or data sets that are linked to the published article"
- For DSpace, this could be the item handle assigned by the repository.
- However, it might be tricky to link a data set to the associated article.
- If the data set resides outside of the repository, this could be captured by a metadata field on the journal article which stores the location (URL) of the data set
- Copyright License Conditions (Also mentioned in "Requisite Conditions")
- includes embargo information
- See comments under "Requisite Conditions" above
- Sponsoring/Funding Agency Name - "Link to agency providing funding so that reports can be automatically returned"
- Could just be a new metadata field in DSpace
- If this is primarily used for reporting, it's likely we also need to capture an email address or a URL / identifier. It depends on the decisions around reporting.
- Reporting - "Creates a feedback loop to the federal agency and the PI's research office providing tracking of publications resulting from awards funded by the agency"
- For DSpace, this could be supported via OAI-PMH, if the agencies regularly harvest this information from repositories.
- But, it's unclear if the repository is expected to push this information to the agencies (currently not supported by DSpace)
- Core Usage Statistics - "Reports to authors (and agencies, if desired) include statistical data on usage activity and downloads of their publications."
- DSpace currently captures usage statistics (views/downloads) on all items in the repository
- However, statistics are just displayed in the User Interface. There are not any statistical reports (e.g. emailed reports) generated at this time
- Metadata Exposed to Search Engines
- DSpace exposes all its metadata (for public items) to search engines and tries to keep up with latest SEO best practices.
- SWORD
- DSpace already supports both SWORD v1 and v2 (servers). It also has a SWORD v1 client which can submit content to another system via SWORD.
- OpenURL
May already be present in DSpace, depending what the exact requirements are.
https://wiki.duraspace.org/display/DSDOC3x/Configuration#Configuration-JSPUI/XMLUISFXServer
- Some connections to Digital Preservation Network (DPN)? - "All phases connect with and take advantage of the Digital Preservation Network (DPN)"
...