Skip to content
This repository has been archived by the owner on Dec 22, 2022. It is now read-only.

Further work to manage library location codes/status codes #1760

Open
1 of 4 tasks
pgwillia opened this issue Sep 3, 2019 · 0 comments
Open
1 of 4 tasks

Further work to manage library location codes/status codes #1760

pgwillia opened this issue Sep 3, 2019 · 0 comments

Comments

@pgwillia
Copy link
Member

pgwillia commented Sep 3, 2019

Is your feature request related to a problem? Please describe.
Currently, library location codes and status codes are managed in multiple yaml files, and each time when they change (and they change often!), it requires a new release of the Discovery service. We need to find a better way to manage these library codes/status codes.

Progress was made in #1742 but further work is required to make better use of this start.

  • SPIKE - can you have the same migration in two applications
  • SPIKE - gemify?
  • Implementation of NEOS Discovery
  • Refactor for SolrMarc

Describe alternatives you've considered
There may be an opportunity to use Symphony WS to lookup/seed this information. If that's not possible a nightly dump might work to get updates.

Additional context
#1297

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant