# Intake 2: The future **URL:** \ **Category:** Technical\ **Tags:** python, data, catalogue, intake\ **Created:** [4 October 2023 01:36 UTC](https://forum.access-hive.org.au/t/intake-2-the-future/1471 "2023-10-04T01:36:44Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Aidan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aidan/32/42_2.png) [@Aidan](https://forum.access-hive.org.au/u/Aidan)\ **Post date:** [4 October 2023 01:36 UTC](https://forum.access-hive.org.au/t/intake-2-the-future/1471/1 "2023-10-04T01:36:44Z")
# Introduction ACCESS-NRI (@dougiesquire) has developed a “Meta-Intake” catalog of a number of datasets located at NCI. More information is available on his workshop poster: > [@Poster: The ACCESS-NRI Intake catalog](https://forum.access-hive.org.au/t/poster-the-access-nri-intake-catalog/1131): > > Title The ACCESS-NRI Intake catalog: a community-driven approach for finding, loading and sharing data on Gadi About The ACCESS-NRI Intake catalog provides a simple, community-driven approach to finding, loading & sharing ACCESS & ACCESS-related model data on Gadi. The catalog can be used from within your Python environment to discover & load data that meet your research needs without having to know where the data are or how they fit together. It’s also easy to add your data to the catalog so t… # New developments Martin Durant ([orcid.org/0009-0007-2516-6831](https://orcid.org/0009-0007-2516-6831)) is working on Intake 2, an ambitious redesign of Intake that would make it significantly more capable and extensible. He presented some of the work he has already done and his proposed design in a pangeo showcase to get feedback from the community about what they needed, and if, in fact, this was a useful thing to do: > **[Sep 27, 2023: "Intake 2: The Future", Martin Durant](https://discourse.pangeo.io/t/sep-27-2023-intake-2-the-future-martin-durant/3706)** > > \[DOI\] \[Intake 2: The Future\] I was particularly interested in the proposed support for pipelines: intake catalogs could be of data, or views into transformations of multiple datasets. This would be a very useful capability. A catalog could contain an entry into raw model data, as well as a CMORised view of the same data, with altered meta-data, to be compatible with tools that require CMORised inputs, e.g. ESMValtool. It would also be possible to have the same data available at different resolutions targeting specific use-cases, and generate the regridding on the fly. Combine that with proposed support for caching and it would be possible to offer a number of different regridded end-points that could be dynamically generated, with the most used retained in the cache. This is potentially quite transformative. ---
**Author:** ![Aidan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aidan/32/42_2.png) [@Aidan](https://forum.access-hive.org.au/u/Aidan)\ **Post date:** [4 October 2023 01:46 UTC](https://forum.access-hive.org.au/t/intake-2-the-future/1471/2 "2023-10-04T01:46:48Z")
@fmccormack Data was a big focus in the most recent [cryosphere working group meeting](https://forum.access-hive.org.au/t/cryosphere-working-group-meeting-minutes-2023/689/5), which prompted me to write this up as a forum post, as I think the pipeline capability is a very interesting one. It would certainly lower the barrier to using ACCESS model outputs in your ice-sheet models, and vice-versa.