| Page Properties | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Background
Because the ingestion of updates and new data will have an effect on all institutional as well as the consortial Primo views, the procedure and schedule through which current and new data pipes are run needs to be transparent. In addition, campuses need a procedure to get new local data sources into the consortial Primo knowledgebase.
Policy Statement
This policy describes best practices for Primo publishing pipe configurations and schedules. It may address how changes are submitted, determined and implemented.
...
Pipes will be scheduled so as to have the lowest impact possible on resource availability during peak use times.
The PPM will maintain a public schedule of pipes and report on the results, run time, and success/failure of each pipe run (example: https://docs.google.com/spreadsheets/d/1Q5NUGJqFnIUJCLgUs453h5GT_SEQsWR-_7l7tTcq0gQ/edit#gid=2053023031).
The scheduling will be subject to consensus across the consortium, and may change depending on how many pipes need to run, and how often each pipe needs to run.
The following sample schedule is initially recommended to run seven days a week. (source: https://www.orbiscascade.org/current-alma-and-primo-publishing-schedule/)
Primo publishing pipe starts at 4:30 AM
Primo dedupe pipe starts at 5:30 AM
Indexing and Hotswapping job starts at 6:00 AM
Updating normally occurs around 9:00 AM
...