Skip to content
This repository has been archived by the owner on Nov 26, 2019. It is now read-only.

Promoting file to independent (non-child) work #1135

Open
HKativa opened this issue Jul 23, 2018 · 1 comment
Open

Promoting file to independent (non-child) work #1135

HKativa opened this issue Jul 23, 2018 · 1 comment
Milestone

Comments

@HKativa
Copy link

HKativa commented Jul 23, 2018

Desired functionality related to #1024:

Scenario: A file set consisting of multiple views of an instrument are ingested as a single work. During cataloging, it is discovered that one of the photographs actually depicts a different instrument (for example, see work g732d985s). Accordingly, cataloger wants to promote individual file to a separate work, as opposed to deleting file and re-uploading as a new work.

Functionality in development as of 7/23/2018 for promoting a file to a child work does offer a two-step work-around:

  1. Cataloger promotes an individual file to a child work.
  2. Cataloger deletes relationship to child in record for what becomes the parent work when the file is promoted.

After the functionality for promoting a file to a child work is implemented, we should revisit the need for functionality to promote an individual file to a separate work, specifically are there enough use cases to warrant implementing this as a separate feature or is the work-around described above sufficient to meet our needs.

@HKativa HKativa added this to the Backlog milestone Jul 23, 2018
@eddierubeiz
Copy link
Contributor

Thank you for describing this so concisely. A developer's dream.

@eddierubeiz eddierubeiz changed the title Promoting file to work Promoting file to independent (non-child) work Sep 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants