I think I can push along this thread by conflating the ideas of a customizable landing page and an automatic rendering of the meta/data tables.
But first: I completely agree that ingest should not require the user to create a customized landing page. Instead, the platform should autogenerate a simple HTML summary of the cataloging metadata (citation and description fields) and maybe basic file level metadata (number, size, etc). That would be the descriptive landing page.
To my mind autogenerating this HTML landing page would consist of making internal calls against the study metadata and file data store. Those internal calls would probably include a pulling a subset of the cataloging information, the basic summary of the files (number, name, size), and perhaps variable level metadata from indexed data files.
Those internal calls would return JSON that would be formatted as HTML and plugged into the default descriptive landing page. There would then be a "click here to customize landing page" option that would let advanced users edit the default and create whatever they want.
So what I mean by "automatic rendering" is user level access to those metadata calls returning JSON and/or HTML views. What I mean is that for any study you can pull one of a set of metadata views:
- basic subsets (basic, DC, full)
- table of files (names, sizes)
- table of file variable or other indexed per file metadata.
Once you create these views for the purposes of creating a default landing page, the user would have access to them to reuse those views in their customized version of the descriptive landing page. Or they could reuse those views on their personal websites. Or where ever.
And what I would really like to see in those views (and here is where I am sure I've gone off the deep end) is file previews including:
- Image previews
- Indexed tables rendered as JSON or HTML views
- File level metadata (metadata harvested from individual files) as a table.
I am sure that for as clear idea appears in my head, it is equally likely I am leaving out enough information to render it pretty opaque to any of you. But maybe we can work this out through more discussion.