Split multi-inventory datasets into their constituent parts

[jmalczyk]

This is as much a database and api based issue as a front-end enhancement here. We need to establish a parent-child relationship within our dataset registry, and re-register components of large datasets to have their own dataset ids, with a parent id referencing the larger collection that came from. This could also be applied to very large aggregate datasets like GBIF.

In the datasets UI, in order to keep the full dataset table list from needlessly exploding, we would expose these as individual datasets via an overall view of their parent (such as https://mol.org/datasets/325306dd-4fde-4c21-8518-16d9d916cee9) with yet to be determined selectors and map controls.

[funkycoda]

ETA

• API: 23 Aug
• UI: 25 Aug

[funkycoda]

Dependant on this: https://github.com/MapofLife/database/issues/336

[villanueval]

I'm gathering the title and citations for the children datasets of the checklist_journal dataset. Once I have these, I can prepare the data registry and api to display the children with the parent dataset.

[walterj]

FYI: Other multi-inventory much higher priority. But ok to start with this one if seemingly best suited for start. W

On Aug 18, 2016, at 21:14, Luis J. Villanueva notifications@github.com<mailto:notifications@github.com> wrote:

I'm gathering the title and citations for the children datasets of the checklist_journal dataset. Once I have these, I can prepare the data registry and api to display the children with the parent dataset.

You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3Agithub.com_MapofLife_datasets_issues_53-23issuecomment-2D240826373&d=CwMCaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=sGE6-4YjFTYoObPo4Jnr_be8nXBrXbWU8rllCjefOJo&m=MVBbyq3aJiN-FgSVMqOgqM18MVxI7K_OJ_IR_asYCxw&s=mHbQ7cgaMkOVAMuQXp-IFmxtK326-XlocOV13-MaMCA&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3Agithub.com_notifications_unsubscribe-2Dauth_AAcc9Om2o-2Dp39QAPhcpLRjDuZDlZJALvks5qhK76gaJpZM4Jjt9C&d=CwMCaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=sGE6-4YjFTYoObPo4Jnr_be8nXBrXbWU8rllCjefOJo&m=MVBbyq3aJiN-FgSVMqOgqM18MVxI7K_OJ_IRasYCxw&s=vq2KJ-mz4dgPRI773hI-qhA1WW3O5pQw0fEiWpC5qI&e=.

[funkycoda]

Walter, I think this is the one with a smaller list (30?) so wanted to test out how it would work before we go with the larger ones.

Do you have a suggestion for a priority list, potentially?

[walterj]

Important for e.g. New World bird checklists, national park checklists.

Next should be atlas datasets (but they may be more involved).

Walter

From: Ajay Ranipeta [mailto:notifications@github.com] Sent: Thursday, August 18, 2016 6:52 PM To: MapofLife/datasets Cc: Jetz, Walter; Comment Subject: Re: [MapofLife/datasets] Split multi-inventory datasets into their constituent parts (#53)

Walter, I think this is the one with a smaller list (30?) so wanted to test out how it would work before we go with the larger ones.

Do you have a suggestion for a priority list, potentially?

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3Agithub.com_MapofLife_datasets_issues_53-23issuecomment-2D240880886&d=CwMCaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=sGE6-4YjFTYoObPo4Jnr_be8nXBrXbWU8rllCjefOJo&m=zYvR3rrvzUr4pP2Uyo8ViHXTVnLbiHZw_UfuWqDjam0&s=kzMcFviR4FLYpXvnUDYiFPPu0_it5-_pf5O2GqG8KVU&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3Agithub.com_notifications_unsubscribe-2Dauth_AAcc9PVNj-5FkJv6gpB-5F-5FXTeTjxFL8DqlCks5qhOIngaJpZM4Jjt9C&d=CwMCaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=sGE6-4YjFTYoObPo4Jnr_be8nXBrXbWU8rllCjefOJo&m=zYvR3rrvzUr4pP2Uyo8ViHXTVnLbiHZw_UfuWqDjam0&s=fEahf42mWtlSKWNCSqlQKkG6J1QVJyx1q8ZY0kDTtRI&e=.

[villanueval]

Rafe, check the example dataset with children at:

https://mol.org/datasets/7d2d87f2-82a3-42a8-9f76-db5bb21f2c9a

https://api.mol.org/0.x/datasets/info?dataset_id=7d2d87f2-82a3-42a8-9f76-db5bb21f2c9a