As we ingest metadata from 3rd party repositories we need a means of promoting certain metadata such, as the URL to the source, and displaying it prominently as part of the dataset view. We envision a panel on the right hand side that will display all these promoted metadata fields prominently for the user. Additionally when we access clowder through the API from other applications, we can include this promoted metadata as part of the information returned, not requiring a second query to get this information. For example if we have a field in the metadata that links to the remote location of the data (say url) and this is promoted in the space, when the user requests information about the dataset, besides the normal information such as name, author, it will also return this additional field (in this case url).
-------------------------------------------
Michael Bobak do we want to create additional proposals to capture the following as well? It is easier to have a single page per proposal.
Presently our users have something like a focused google-dataset-search, (via aggregated metadata), that given a query returns potential hits with: Title (w/link to the page w/the data), Abstract, & a metadata ('details') link.
1: The metadata-tab is a great replacement for the 'details'; the only thing that is needed would be to have that tab selected when you get to the page. Especially given that the Clowder dataset is presently a stub to hold the metadata; it has no files. So files is a bad default tab.
2: Since the 'Title' now links to the interim Clowder stub page, I've added the link to the data page at the end of the description. So it will still show up in the search results. It often but not always ends up as a clickable link. If it was more consistent it would be a more useable search.
3: It has been suggested that we have a per space config to select some choice metadata to put in the upper right of the dataset page, e.g. the dataset-landing page.
4: Also, to get a google-dataset-search experience, it has to be done w/o a login, it turns out that doesn't presently work right now: https://github.com/clowder-framework/clowder/issues/83
5: I had also considered just using the Clowder API, to hook into our present web page at one point.
One thought there was having something like a gDoc read-only link, or in this case a key, or there could be a search-user w/read-only access to all the metadata of interest.
6: It would be nice to have the preview image be able to display the space's logo-image, especially as there are not files to preview, &that is what our users have come to expect.
7: I've been experimenting w/carrot2 clustering of search results, which I hear there is a plugin for.
8: We can presently search by any combination of repository/spaces, via checkbox, which might be possible, but I'm not sure how it is done offhand. There is the hourglass for (just one) space, but then we get also into having to pick a facet, and none of them are from the uploaded jsonld.
9: I really like the metadata-search page, but most of our repos (&other aggregators) also allow for selecting a geo-bounded box from a map. As almost all our datasets have lat/lon coordinates in their jsonLD metadata. It will be a feature this geoscience based search will need.
We continue to make use of science-on-schema.org & DCAT2 which has a schema.org mapping. This along w/CSVW also makes the data discoverable via google dataset search. Though our more focused faceted search should be of even more use to the EarthCube search users.