Info page refactoring - HTTP proxy creation

[michael-conway]

This is currently underway at NIEHS and a good thing for bootstrapping some discussion

• create a /emc-metalnx-web/info/zone/home/foo URL mapping as a GET op in a controller
• the url resolves to a standard, bookmarkable http proxy for iRODS files and collections targeted at permanent identifiers and linked data, as well as modes of 'sending a file' via a link, so tickets can be used, url shortening may be used.

The info pages represent one data object or collection, previews, metadata, permissions, sharing, in place editing, as well as replica management and mime/info-type appropriate additional tools and functions.

For us, it's important to pretty quickly get image previews in place for genomics quality control data.

The page can contain structured data microformats (JSON-LD seems the hot topic with the NIH commons)

This is where metadata templating and bulk metadata operations can be hooked in. (add avus to all entries in a collection)

We are currently putting in the basic pages, trying to define a notion of a 'data profile'. This is a ripe candidate for v5 API.

The Data Profile carries things like this:

https://github.com/DICE-UNC/jargon-extensions-if/blob/issue21/src/main/java/org/irods/jargon/extensions/dataprofiler/DataProfile.java

Which could represent a cross-platform, cross-site view of some very standard concepts found in commodity cloud-based file sharing environments.

The question is can such concepts be represented in an abstract way that could accommodate existing implementations. For our part we want to create an 'irods-ext' implementation that adopts the MetaLnx conventions and would support eventual migration towards some mean as versions change.

[michael-conway]

NB this move allows the 'collections' browser function to be leaner, and that allows work to factor in virtual collections and query support in later issues.