search

UNC-Libraries / Curators-Workbench

This project has been archived and is no longer being developed or supported. The Curator's Workbench is an extensible digital collection and appraisal tool for the desktop. It is designed to acquire and process batch data efficiently while giving the user control over work flow.
http://blogs.lib.unc.edu/cdr/index.php/about/cdr-development-and-collab/curators-workbench/
24 stars 0 forks source link

Ability to manage project staging locations, trigger migration #16

Open jjksexton opened 13 years ago

jjksexton commented 13 years ago

The only chance the user has to set the staging location for a project is during the initial steps of project creation. After that step in the process, there is no opportunity to revise or even to view the current staging settings. It would be nice to be able to view a project's staging settings, and to be able to change the staging location. This is especially true in cases where a project is staged to a test environment before eventually moving to a production environment. In the current design the user would have to create an entirely new project.

gregjan commented 12 years ago

I want to rephrase this a bit, in light of recent requests and an imagined work flow. I would call it, "Ability to add new staging locations to a project and replicate staged files." This will support the use case of staging to a portable hard drive, then transferring to a more stable network staging location later.

gregjan commented 11 years ago

Stages should have the option of having a manifest URI that is more portable than the local file URI for a mapped drive. The workbench would only use the manifest form in the METS.

This would mean that Mac and PC users could exchange projects, so long and each had a staging location with matching manifest URIs.

E.G. Storhouse Born Digital local URI: file:/z:/born_digital/ manifest URI: http://storhouse.lib.unc.edu/born_digital/