Allow blank site_id, instrument_id, telescope_id #72
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
Some data products, such as FLUXSTANDARDs need to be accessible in the archive but are not associated with a particular site/tel/inst
This seems incorrect.
I am not sure why the makemigrations script wanted to remove the frames_aggregate index, but we don't want that.
makemigrations script is adding in a lot that isn't necessary.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allow for blank site, instrument, telescope. This allows us to store data products that aren't necessarily associated with a physical telescope but that still need to be served to users.
I have this running in LCO's dev cluster at http://archive-api-dev.lco.gtn/frames/
An example of a non-telescope data product that has been ingested to the archive: http://archive-api-dev.lco.gtn/frames/3723