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

Update Locations for ACMA #17

Open
crugas opened this issue Dec 20, 2024 · 1 comment
Open

Update Locations for ACMA #17

crugas opened this issue Dec 20, 2024 · 1 comment
Assignees

Comments

@crugas
Copy link
Collaborator

crugas commented Dec 20, 2024

ACMA needs to add several spreadsheets worth of new Locations. To use the Locations CSV, the CAAS team will need to update newly added locations to associate them with ACMA. Mark created a script previously, found here, to quickly update added Locations provided a CSV is used containing the URIs of the newly added Locations.

Mark advised that we have ACMA add the new locations to ASpace, then generate a CSV of the newly added Locations from the ASpace SUI sorting by date added - greater than that day's date - containing the URIs of all the Locations added. Then we can run the above script or a modified version of it to associate it with ACMA repository.

TODO: Once this is completed, make sure to resolve SCTASK0189884 in ServiceNow.

@crugas crugas self-assigned this Dec 20, 2024
@fordmadox
Copy link
Contributor

In addition to the CSV download from the staff interface, here's the hacky SQL that I found that I used previously to get a list of locations that might need to be updated (but the Udvar-Hazy examples where AAA materials are stored is a good reason, I think, not to assign the repository data point):

SELECT CONCAT('/locations/', location.id) AS url, location.title
from location
LEFT JOIN owner_repo_rlshp orr ON location.id = orr.location_id
WHERE orr.repository_id IS NULL;

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

2 participants