Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store snapshots of EAD from ArchivesSpace for staff #467

Open
kelynch opened this issue Nov 9, 2020 · 3 comments
Open

Store snapshots of EAD from ArchivesSpace for staff #467

kelynch opened this issue Nov 9, 2020 · 3 comments

Comments

@kelynch
Copy link

kelynch commented Nov 9, 2020

To support staff workflows for accessing older versions of EAD (currently supported in PULFA 2), store ArchivesSpace EAD snapshots somewhere external to PULFAlight, accessible to staff.

The use case for this is to support researchers wanting to know how an EAD looked in the past. "what has been added or re-described since the last time I looked at this collection?"

@kelynch kelynch changed the title Store EAD from ArchivesSpace in SVN for staff Store snapshots of EAD from ArchivesSpace for staff Nov 9, 2020
@escowles
Copy link
Member

ASpace has "revision statements" that are similar in function to SVN commit messages — used to indicate why a change was made. These would be useful for knowing why changes were made, recording changes made as part of systematic projects to improve descriptions, etc.

@faithc
Copy link
Collaborator

faithc commented Aug 11, 2021

We would also want to make these available to users as well.

@kelynch
Copy link
Author

kelynch commented Sep 16, 2021

A primary goal that has been discussed for this issue is to set up a git server, convert the SVN repository to git, and migrate the git repository to the new git server. Users could then access the repository via the git plugin for Oxygen, among other methods.

A process would need to be developed to sync EAD content from ASpace to the git repository periodically (for example, weekly or monthly).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants