The @type key for the serialized identifiers, could be more specific based on the related_identifier.resource_type field.

Instructions should be included for using docker with access to cvmfs and conddb (as pointed out by the CMS Open Data users at MIT).

Could someone explain (or give example) to me how can I use taxonomy fields? I've created simple thesaurus that contains hierarchy (broader, narrower). Using the solr admin panel I can query documents that contain fields "tag_ss_taxonomy_X_ss" but how can I use those fields in search?

For example, I have 2 fields:
`"tag_ss_taxonomy_0_ss":["Human",
"Human",
"Human",

Since some checks may be run without others and the file will be simply modified, could be helpful to include a header in each output sheet with the date, e.g. "HFC 9 as of 2017/03/18".

• Consider the usefulness of having the docs split (main & client) or merged.
• In any case, it would be worth having better visibility of the docs from the site.

Consider this "FAIR-TLC" rubric for Metrics to Assess Value of Biomedical Digital Repositories

We also applied it to the NIH/WellcomeTrust Open Science prize candidates to evaluate the rubric:
Musings on the Open Science Prize

Slides presenting the rubric are [here](https://www.slideshare.net/mhaendel/how-o

As per: http://repo2docker.readthedocs.io/en/latest/usage.html#preparing-your-repository

At the same time, it makes sense to split up the README so the appropriate focus is possible in context.

This would get us:

/
|
+--binder/
|   |
|   +--README
|   |
|   +--requirements.txt
|   |
|   +--postBuild
|
+--notebook/
|   |
|   +--README
|   |
|   +--projects/
|
+--README

This page let's you test out regular expressions. Do we already have a chapter about the importance of regular expressions? We should.
I found this link in the DataCamp Course "Intermediate R - Practice"