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

Course Reserves temp bibs aren't showing the right material type consistently when created #67

Open
MargaretA-UO opened this issue Nov 18, 2022 · 3 comments
Labels
on hold Don't work on this - there are questions or we're waiting for more information

Comments

@MargaretA-UO
Copy link

This is a solution that Jeremy McWilliams put together for Lewis & Clark, and we wanted to ask if you thought this could be workable for UO, please.

https://github.com/watzek/add-972-to-bib

I'm not sure we'd need to have it run daily - probably on demand, since the creation of these temporary records clusters at the beginning of terms.

Thank you.

@jechols
Copy link
Member

jechols commented Nov 18, 2022

I don't know enough about the Alma setup we have to say much about whether this would work for us. I think I'd have to set it up to do some kind of "dry run" and see what it would do, and share that with you.

I'd probably rewrite the thing anyway so it's more supportable on our side - Python might make a lot of sense since it's pretty ubiquitous at this point, though Go may be a good choice, too. PHP maintenance has been iffy in the past, and it's not a "core" language for most of us in ADI anymore (I'm probably the PHP "expert" at this point, and that's terrifying).

I'm not sure about running on demand - that kind of thing always bites us in the end - I'll be out on vacation or something, and somebody else will struggle for 4 hours because my "perfect" documentation was missing a crucial step.... Unless there's a reason to definitely avoid a regular run, I'd want to let it do its thing regularly.

Side note, mostly to me: this could probably run on lib-ilsutils. We have so much going on there already that's related to alma/primo. Usually stuff that's highly sensitive, but it's still not a bad place to centralize automated tasks that are ILS-related.

I will try to look at this today, but it may have to wait depending on some other issues going on right now.

@jechols
Copy link
Member

jechols commented Nov 18, 2022

Hmm.. we'd also probably want either email notifications (which we already have in other Python scripts on lib-ilsutils) or Teams notifications (which we've never done and probably isn't worth the time anyway) so that somebody can see what the script did....

And some serious in-depth logging. Which we also have an okay framework for in our other Python scripts on lib-ilsutils.

@jechols
Copy link
Member

jechols commented Nov 18, 2022

Per our conversation, this is on hold pending more information.

@jechols jechols added the on hold Don't work on this - there are questions or we're waiting for more information label Nov 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
on hold Don't work on this - there are questions or we're waiting for more information
Projects
None yet
Development

No branches or pull requests

2 participants