An interesting question was raised by @charles-turner-1 this morning - how portable is access-nri-intake-catalog? For example, would another institute be able to pick it up and use it to manage/store their own collection of climate models without having to make structural changes to the code base? (As in, changes to the base-level code, not just adding Builders/Translators are required.)
What jumps out to me at first is:
- I think most of the paths that are set inside the package are variables, so that should be able to be easily modified;
- I think the code that deals with storage flags, storage access etc. is hard-coded to expect
/g/data-style paths - that would need to change if we wanted to make the package more portable.
An interesting question was raised by @charles-turner-1 this morning - how portable is
access-nri-intake-catalog? For example, would another institute be able to pick it up and use it to manage/store their own collection of climate models without having to make structural changes to the code base? (As in, changes to the base-level code, not just adding Builders/Translators are required.)What jumps out to me at first is:
/g/data-style paths - that would need to change if we wanted to make the package more portable.