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
Integration with GCRcatalogs #106
Comments
I'm starting to formulate a design for this. But first I'd like to see changes in the way the production dataset is created and handled. It's a separate issue, but related in that dealing with these legacy datasets will be our first serious use of production. At NERSC, production datasets will be under the existing shared area, Assuming something like the above has been done, adding a new dataset for an existing dataset known to GCRCatalogs is straightforward for "simple" (explained below) catalogs: call dataset.register as usual with |
Noting that, as @stuartmcalpine suggested, some notion of "collection", similar to the concept in Rucio, may help with composite catalogs. |
@yymao your thoughts on this issue would be most welcome! |
Can we replace aspects of GCRcatalogs with the registry?
For example, people would register the GCRcatalogs configuration files into the registry rather than hard coding them into the GCRcatalogs code.
Can we scrape these config files in a useful way to make ingesting them a bit easier?
The text was updated successfully, but these errors were encountered: