This repository has been archived by the owner on Dec 22, 2022. It is now read-only.
[Spike] CirculationRules and ItemType models to align with Discovery #477
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Both Discovery and NEOSDiscovery use Symphony configuration data to provide human readable string in the holding table. Additionaly NEOSDiscovery has library/location relationships. We now have this data flowing into Discovery but we need this to continue to flow into NEOSDiscovery. One way to do this would be to use the same migrations on both applications. Here we create two tables that will not be used by the application in the interest of being compatible with Discovery symphony_nightly migrations.
pgwillia
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Both Discovery and NEOSDiscovery use Symphony configuration data to provide human readable string in the holding table. Additionaly NEOSDiscovery has library/location relationships. We now have this data flowing into Discovery but we need this to continue to flow into NEOSDiscovery. One way to do this would be to use the same migrations on both applications.
Here we create two tables that will not be used by the application in the interest of being compatible with Discovery symphony_nightly migrations.
#352