{"id":12932,"date":"2014-09-08T16:26:10","date_gmt":"2014-09-08T15:26:10","guid":{"rendered":"http:\/\/www.ch.imperial.ac.uk\/rzepa\/blog\/?p=12932"},"modified":"2014-09-17T06:51:45","modified_gmt":"2014-09-17T05:51:45","slug":"one-molecule-one-identifier-viewing-molecular-files-from-a-digital-repository-using-metadata-standards","status":"publish","type":"post","link":"https:\/\/www.ch.ic.ac.uk\/rzepa\/blog\/?p=12932","title":{"rendered":"One molecule, one identifier: Viewing molecular files from a digital repository using metadata standards."},"content":{"rendered":"
\n

In the beginning (taken here as\u00a0prior to ~1980) libraries held\u00a0five-year printed consolidated indices of molecules, organised by formula or name (Chemical abstracts). This could occupy about 2m of shelf space for each five years. And an equivalent set of printed volumes from the Beilstein collection. Those of us who needed to track down information about molecules prior to ~1980 spent many an afternoon (or indeed a whole day) in the libraries\u00a0thumbing through these weighty volumes. Fast forward to the present, when (closed) commercial databases such as SciFinder, Reaxys and CCDC offer information online for around 100 million molecules (CAS indicates it has 89,506,154 today for example). These have been\u00a0joined by many open databases (e.g.<\/em>\u00a0PubChem<\/a>).\u00a0All these\u00a0sources of molecular information have their own way of accessing individual entries, and the wonderful program Jmol (nowadays JSmol<\/a>) has several of these custom interfaces programmed in. Here I describe some work we have recently done[1]<\/a><\/span> on how one might generalise access to an individual molecule held in what is now called a digital data repository<\/em><\/strong>.<\/p>\n

Such repositories are gradually becoming more common. Unlike most (all?) of the bespoke molecular repositories noted above, metadata (XML<\/a>) resourcemap standards have been developed[2]<\/a><\/span> for data repositories to enable\u00a0rich and open searches<\/a>\u00a0and to help in the discoverability of individual entries (e.g.\u00a0<\/i>OAI-ORE<\/a>). Each dataset\u00a0is characterised by\u00a0a DOI (digital object identifier), just like individual\u00a0articles found in a conventional\u00a0journal. However, there is an issue in\u00a0quoting just a conventional DOI to describe a dataset. The DOI points to what is called the article\u00a0landing page<\/em>\u00a0in the journal. A landing page which\u00a0by and large is meant to be navigated by a human. To get a flavour for how this works (or more accurately does not work) for data, visit this DOI[3]<\/a><\/span> for an entry in the CCDC crystal database noted above (and about which I have previously blogged<\/a>). In essence, a human is needed to complete the requested information in order to proceed to retrieving the data. Data, I contend here,\u00a0should not\u00a0need a landing page. It can benefit from being passed straight on to e.g.<\/em> a visualising program such as JSmol. So a mechanism is needed to encapsulate any bespoke (and potentially changeable) access path to the data by expressing it instead in standard metadata form.<\/p>\n

In our first solution to this issue, and the one illustrated here, we used a standard known as 10320\/loc[2]<\/a><\/span>. A datafile need only be specified by its DOI (or more generically, its handle) to be recovered\u00a0from the data repository; no landing page need be involved (and no human need ponder what next to do with the data).<\/p>\n

    \n
  1. First, let me reference a molecule (as it happens the one described in the preceding post<\/a>), using the normal invocation[4]<\/a><\/span>. This will take you to a conventional landing page.<\/li>\n
  2. The next example is the same dataset, but this time with the landing page replaced by a Javascript\/JSmol wrapping. This is achieved using a utility which is\u00a0itself packaged up and placed on a repository (shortdoi: vjj<\/a>)[5]<\/a><\/span>, and which is embedded here for you to try out. If you want the technical detail, read about it here.[1]<\/a><\/span><\/li>\n<\/ol>\n