Scripts that are dependencies - identify and document for operational support

[libdgg]

• [ ] Identify any scripts (e.g. newly acquired items ticket) that Library Search is dependent on
• [ ] add this information to the wiki
• [ ] in the wiki documentation, please indicate the names/roles of people in LTDS that have the permissions/access to support them going forward

[AGCooper]

On turing.library.emory.edu Newly acquired:

• crontjobs: /alma/bin/newly_acquired.sh /alma/bin/new_ebooks_process.sh

• Scripts (all in /alma/bin/): new_items_analytics_list.py new_items_create_xml.py new_and_pending.py new_and_pending.sh new_check_pending.py new_pending_items_process.sh new_items_put.py old_items.sh (probably broken)

OR:

https://github.com/emory-libraries/Alma-Public/tree/master/NewlyAcquired

https://github.com/emory-libraries/Alma-Public/tree/master/NewEbooks

Alma users:

• Crontjobs: /alma/bin/scp_retrieve_borrower.sh /alma/bin/borrower_process.sh

• Scripts: /alma/bin/borrower.py

OR:

https://github.com/emory-libraries/Alma/tree/master/PatronLoader

[AGCooper]

On kleene.library.emory.edu Aeon integration:

cgi-bin:

/usr/local/cgi-bin/process_booking_primo_new

Sccripts: /sirsi/webserver/bin/process_primo_request.py /sirsi/webserver/config/process_booking_primo_new.cfg /sirsi/webserver/docs/process_booking_request.html

OR:

https://github.com/emory-libraries/Primo-BG/tree/master/Alma-based-requests

[AGCooper]

Not sure how much more detailed we can get without explaining programming.

[libdgg]

@AGCooper I added the checklist of steps to the description of this ticket to complete this work.

[lovinscari]

I am going to close this ticket as we will need to address how we are going to finish the operational work for Library Search and DLP (and other products) in a different forum.