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.

Sign up for GitHub

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

Jump to bottom

Provide descriptive titles to links in location_changes.md #2215

Merged
merged 3 commits into from
Jul 26, 2023
Merged

Provide descriptive titles to links in location_changes.md #2215

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ea9465c
Provide descriptive titles to links in location_changes.md
lizgarciao Jul 26, 2023
3eca026
Title first link as "Alma Config repository"
lizgarciao Jul 26, 2023
ed4f48d
Include Christina's suggestions
lizgarciao Jul 26, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 11 additions & 11 deletions docs/location_changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
# When a location changes in Alma:
* A ticket should be created first in https://github.com/PrincetonUniversityLibrary/alma-config/issues with all the necessary information.
* A ticket should be created first in [Alma Config repository](https://github.com/PrincetonUniversityLibrary/alma-config/issues) with all the necessary information.
## 1. Update the local dev environment:

1. Update the necessary files in https://github.com/pulibrary/bibdata/tree/main/config/locations.
* If there is a new holding location then update the holding_locations.json file https://github.com/pulibrary/bibdata/blob/main/config/locations/holding_locations.json with the appropriate information.
* If there is a new library then update the libraries.json file https://github.com/pulibrary/bibdata/blob/main/config/locations/libraries.json with the new library following the pattern in the file.
* If there is a new delivery location then update the delivery_locations.json file https://github.com/pulibrary/bibdata/blob/main/config/locations/delivery_locations.json with the appropriate information.
1. Update the necessary files in [bibdata locations directory](https://github.com/pulibrary/bibdata/tree/main/config/locations).
* If there is a new holding location then update the [holding_locations.json file](https://github.com/pulibrary/bibdata/blob/main/config/locations/holding_locations.json) with the appropriate information.
* If there is a new library then update the [libraries.json file](https://github.com/pulibrary/bibdata/blob/main/config/locations/libraries.json) with the new library following the pattern in the file.
* If there is a new delivery location then update the [delivery_locations.json file](https://github.com/pulibrary/bibdata/blob/main/config/locations/delivery_locations.json) with the appropriate information.

2. Run the following rake task to delete the existing data from the location tables and repopulate them using the config files:
`bundle exec rake bibdata:delete_and_repopulate_locations`
Expand All @@ -20,7 +20,7 @@
6. Load locally the rails server; Go to: `localhost:<portnumber>/locations/holding_locations` in your browser and make sure that the locations have been updated.

## 2. Update Bibdata staging
Test the updated locations in Bibdata-staging https://bibdata-staging.princeton.edu/
Test the updated locations in [Bibdata staging](https://bibdata-staging.princeton.edu/)
Deploy your branch on staging and run the following steps to make sure that nothing is breaking the tables.

1. Connect in one of the bibdata staging boxes:
Expand All @@ -30,10 +30,10 @@ Deploy your branch on staging and run the following steps to make sure that noth
2. Run the following rake task to delete and repopulate the locations in the bibdata staging database:
`RAILS_ENV=production bundle exec rake bibdata:delete_and_repopulate_locations`

3. Review the changes in https://bibdata-staging.princeton.edu/
3. Review the changes in [Bibdata staging](https://bibdata-staging.princeton.edu/).

## 3. Update Bibdata qa
Test the updated locations in Bibdata-qa https://bibdata-qa.princeton.edu/
Test the updated locations in [Bibdata qa](https://bibdata-qa.princeton.edu/).
Deploy your branch on qa and run the following steps to make sure that nothing is breaking the tables.

1. Connect in one of the bibdata qa boxes:
Expand All @@ -43,11 +43,11 @@ Deploy your branch on qa and run the following steps to make sure that nothing i
2. Run the following rake task to delete and repopulate the locations in the bibdata qa database:
`RAILS_ENV=production bundle exec rake bibdata:delete_and_repopulate_locations`

3. Review the changes in https://bibdata-qa.princeton.edu/
3. Review the changes in [Bibdata qa](https://bibdata-qa.princeton.edu/)

*If it runs successfully merge and deploy to production; go to the next step to update the location tables in production.*
## 4. Update Bibdata production
### Don't update the locations in Bibdata production during indexing hours https://github.com/pulibrary/bibdata/blob/main/docs/alma_publishing_jobs_schedule.md.
### Don't update the locations in Bibdata production during indexing hours. Please see [Alma Publishing Jobs Schedule](https://github.com/pulibrary/bibdata/blob/main/docs/alma_publishing_jobs_schedule.md).

1. Connect in one of the bibdata production boxes:
`ssh deploy@bibdata-alma-worker1`
Expand All @@ -56,4 +56,4 @@ Deploy your branch on qa and run the following steps to make sure that nothing i
2. Run the following rake task to delete and repopulate the locations in the production database:
`RAILS_ENV=production bundle exec rake bibdata:delete_and_repopulate_locations`

3. Review the changes in https://bibdata.princeton.edu/
3. Review the changes in [Bibdata](https://bibdata.princeton.edu/).
Loading