search

pulibrary / RDOS_Publishing

Ticket incubation for the portfolio of infrastructures used by Research Data and Open Scholarship (RDOS) to publish research and scholary objects.
1 stars 0 forks source link

Discovery: Versioning #2

Open hhkitsune opened 2 years ago

hhkitsune commented 2 years ago

Priority

Warm, but not on fire

This is expected to be needed within a currently undefined time-frame to comply with the recent White House memo concerning repositories to deposit federally funded research. We can talk about a more specific time-frame that will work alongside our other priorities.

This feature may fall under the prioritization set by the recent White House memo that points to the "Desirable Characteristics" for requirements to deposit federally funded research data. (See: Table 1., Digital Object Management, Provenance.)

The repository has mechanisms in place to record the origin, chain of custody, version control, and any other modifications to submitted datasets and metadata.

Description

This ticket describes an end-user experience of a versioning feature. ScholarSphere (Penn State) has a versioning feature and is used below as an example of an ideal experience for our end-users.

Important Consideration

We may need to offer a separate restriction feature for accessing previous versions of large datasets.

User Stories

Dr. Mária Telkes, a researcher, searched our Discovery portal for the accompanying dataset to a solar energy study she was duplicating. The study listed a specific version of the data. Dr.Telkes noticed the object's record in our Discovery portal showed a newer version of the dataset. Although interested in the new version, she needed to review the version listed in the journal paper. She was able to choose the previous version needed. An alert banner appeared when accessing this earlier version to let her know it wasn't the most current version.

Isabel Archer, graduate student, was looking for data to reuse in her research project on chemical bonds. She found something potentially useful in our discovery portal. When she accidentally selected an earlier version, a terribly visible banner message let her know this wasn't the newest version of the work.

Sample Information

The sample shows an object in ScholarSphere that is using their versioning feature. (Great work on this feature ScholarSphere team!) The live sample can be accessed here: PSU Scholarsphere version feature sample

The page defaults to the most current version.

Image

When an older version is selected, a bright yellow banner appears at the top of the screen to warn users that this is not the most current version.

Image

Relationship to other issues

This ticket is expected to be only one component of a series of tickets that address versioning and provenance, both for the end-user experience with Discovery and the users (e.g., depositors, curators/collection-admin) experience in Describe.

A related, but different feature is described in ticket #198 which was implemented in the describe form. The feature in #198 records the provenance for actions taken

astrochun commented 1 year ago

The behavior/end user experience you documented is similar on Zenodo and Figshare.