We will use the international conference call dial-in. Please follow directions below.
Discuss and review COAR's 12 user stories that outline priority functionalities for next generation repositories.
The document, to which you can provide public comments directly, is available here: nextgenrepo.coar-repositories.org
Deadline for comments is March 3rd 2017, so we should attempt to combine and send in our feedback before our next DCAT meeting. Comments are submitted through http://comment.coar-repositories.org/
If you can, read or review the document in advance, which will help the discussion.
COAR (Confederation of Open Access repositories) started off as a European project. Originally initiated by institutions from movements like OpenAIRE and to link Open Access repositories in Europe, COAR grew out to a full Open Access organization.
On their 'Next Generation Repositories' website, the organization presents several statements and user stories, which are elaborated upon below. In the early stages of DSpace 7 development these statements and topics can make us focus and refocus on the direction we are currently going.
First of all, COAR stated 4 principles:
Next to these principles COAR also stated 5 design assumptions:
Next to these principles and design assumptions, COAR stated 12 user stories.
"As a human or machine user, I want to easily and uniformly identify the metadata in a repository record, so that I can ascertain the relevance of the resource."
DSpace is currently not exposing any metadata in the urls as it is using handle. But it does include google scholar head tags to facilitate the indexing of content by google scholar. One downside is that although we are doing a thorough job on this, we are only doing it ad hoc for google Scholar. It would be good if we could implement a more broadly accepted standard to make metadata tags machine readable more broadly.
"Web reference managers, annotation tools, or crawlers that encounter a landing page or any other web resource that is part of a scholarly object need to easily identify the associated persistent HTTP URI for the resource, so that they can retrieve it"
Usually URI's refer to metadata records, but persistent URI's to files should be easily visible as well according to this principle. DSpace makes bitstream URL's harder to retrieve on purpose, as those are more subject to change compared to metadata pages.
Despite these efforts, Google often indexes direct links to bitstreams. As these links often break it may be better to make a more persistent link to bitstream, or to entirely stop disposing links to bitstreams. This latter option may also avoid people referring to the bitstream instead of the item page when referring to certain content.
"As a machine or human user, I need to easily and uniformly identify the licensing and re-use conditions of a scholarly resource, so that I know what I am allowed to do with it."
DSpace is currently not exposing any license or re-use information to the end-users. This is something which can be improved in future versions of DSpace.
"As a user, I want my repository to recognize me and other users so that I can be connected with other users who I know, leave comments and be informed of content that is of interest to me."
User stories 4 and 5 are related to each other, we cover them both in this section.
Commenting and annotating could work for some platforms, but it is questionable if this is a good idea for DSpace as well. The question is if we want to expand repository functionality to this level. Such functionality also requires us to be able to identify the user, as an anonymous comment could easily go wrong. An identification through ORCID could be a solution to this problem.
Although we would like to avoid commenting and annotating in DSpace itself, we must acknowledge the large interest in open peer review.
See the user story 4 notes.
This user story was not addressed during the meeting. In case you are willing to share any insight, experience or idea, feel free to do so in the comments below.
This user story was not addressed during the meeting. In case you are willing to share any insight, experience or idea, feel free to do so in the comments below.
This user story was not addressed during the meeting. In case you are willing to share any insight, experience or idea, feel free to do so in the comments below.
This user story was not addressed during the meeting. In case you are willing to share any insight, experience or idea, feel free to do so in the comments below.
This user story was not addressed during the meeting. In case you are willing to share any insight, experience or idea, feel free to do so in the comments below.
This user story was not addressed during the meeting. In case you are willing to share any insight, experience or idea, feel free to do so in the comments below.
This user story was not addressed during the meeting. In case you are willing to share any insight, experience or idea, feel free to do so in the comments below.
Last time, following topics were proposed:
To be determined what we cover in the next meetings.