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

Update location and publishing jobs documentation with current shedul… #2306

Merged
merged 1 commit into from
Jan 30, 2024
Merged

Update location and publishing jobs documentation with current shedul… #2306

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 3 additions & 1 deletion docs/alma_publishing_jobs_schedule.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,9 @@
Note: Jobs are running in Princeton local time.

## Incremental Job
* The job initializes daily every 6 hours, at 4:00am, 10:00am, 4:00pm, 10:00pm. It takes around 60 min to complete and get published.
* The job initializes daily every 2 hours and takes 50 - 60 mins to complete and get published:
- 12:00am, 2:00am, 4:00am, 6:00am, 8:00am, 10:00am,
- 12:00pm, 2:00pm, 4:00pm, 6:00pm, 8:00pm, 10:00pm.

## General Publishing Job
* The job initializes every Friday at 1:00am. It takes 13-16 hours to complete and get published.
2 changes: 1 addition & 1 deletion docs/indexing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ The Alma ILS is the source of princeton's MARC data, both physical and electroni

Alma MMS ids start with 99 and end with 3506421

Frequency of updates: 4x per day: 4am, 10am, 4pm, 10pm see: [Alma Publishing Jobs Schedule](https://github.com/pulibrary/bibdata/blob/main/docs/alma_publishing_jobs_schedule.md)
Frequency of updates see: [Alma Publishing Jobs Schedule](https://github.com/pulibrary/bibdata/blob/main/docs/alma_publishing_jobs_schedule.md)

## Source: SCSB
Around 10 million items shared by our ReCAP Partners, Columbia, NYPL, and Harvard, pulled through [HTC's shared collection software](https://github.com/ResearchCollectionsAndPreservation/scsb).
Expand Down
2 changes: 2 additions & 0 deletions docs/location_changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
# When a location changes in Alma:
* A ticket should be created first in [Alma Config repository](https://github.com/PrincetonUniversityLibrary/alma-config/issues) with all the necessary information. [Alma Config repository](https://github.com/PrincetonUniversityLibrary/alma-config) is a private repository and you may not have access. Please ask if you can gain access.

## 1. Update the local dev environment:

1. Update the necessary files in [bibdata locations directory](https://github.com/pulibrary/bibdata/tree/main/config/locations).
Expand Down Expand Up @@ -48,6 +49,7 @@ Deploy your branch on qa and run the following steps to make sure that nothing i
*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. Please see [Alma Publishing Jobs Schedule](https://github.com/pulibrary/bibdata/blob/main/docs/alma_publishing_jobs_schedule.md).
The indexing takes place after the [Alma Publishing Job](https://github.com/pulibrary/bibdata/blob/main/docs/alma_publishing_jobs_schedule.md) completes and an event is created with a `Finish` timestamp and `Success: true` in bibdata.

1. Connect in one of the bibdata production boxes:
`ssh deploy@bibdata-alma-worker1`
Expand Down
Loading