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

Replacing ETD bulk loader with Bulkrax #300

Closed
kerchner opened this issue Nov 2, 2021 · 3 comments
Closed

Replacing ETD bulk loader with Bulkrax #300

kerchner opened this issue Nov 2, 2021 · 3 comments

Comments

@kerchner
Copy link
Member

kerchner commented Nov 2, 2021

No description provided.

@kerchner kerchner added this to the 1.6.0 milestone Jan 25, 2022
@kerchner kerchner removed this from the 1.6.0 milestone Feb 9, 2022
@kerchner kerchner changed the title Evaluate replacing ETD bulk loader with Bulkrax Replacing ETD bulk loader with Bulkrax Sep 12, 2023
@kerchner
Copy link
Member Author

kerchner commented Mar 5, 2024

The constraint here is that Bulkrax does not appear to be equipped to set embargo statuses -- and certainly not different status for a work's metadata versus its files, as is our practice in GW ScholarSpace. This was confirmed in 2023 via Slack conversation w/Bulkrax developers. Consider contributing an enhancement to Bulkrax to implement this. Alternatively, load ETDs via bulkrax as private, followed by setting embargo statuses, followed by setting visibility to public.

@kerchner
Copy link
Member Author

kerchner commented May 20, 2024

Note that as of samvera/bulkrax@0de8ee0 , the following issues in Bulkrax that we need have been fixed/enhanced:

  • Ability to write CSV with separate lines for parent work and child FileSets
  • Ability to set embargo dates and visibility status in the CSV, for individual items (whether they are works, FileSets, etc.) as follows:
visibility visibility_during_embargo embargo_release_date visibility_after_embargo
embargo restricted 4/19/2024 open

@kerchner
Copy link
Member Author

Implemented in #555 (with #562)

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

1 participant