<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Times New Roman">Hi all,<br>
<br>
Has it been decided how large a chunk of data is going to be
assigned a DOI. Will they be assigned at the DRS atomic dataset
level? Or the DRS "publication-level dataset" level? or what? I
guess the tradeoff is:<br>
<br>
Larger chunks require fewer DOI's<br>
Larger chunks mean that some files will be associated with
multiple DOI's (when a single file in the chunk gets replaced, the
chunk will have to be assigned a new DOI, so all the other files
will now be associated with 2 DOI's). <br>
<br>
We will have to provide a service so a user knows what data is
associated with each DOI. If a given subset of a chunk of data is
associated with multiple DOI's, a reference to either DOI should
point to the same (identical) subset of the data.<br>
<br>
Is this confusing?<br>
<br>
best regards,<br>
Karl<br>
</font><br>
On 11/16/10 5:22 AM, Martina Stockhause wrote:
<blockquote cite="mid:4CE2857B.70205@zmaw.de" type="cite">
<pre wrap=""> Hallo Bryan, dear all,
we started to set up the mirror pages of your DOI target page. It is
very rough, since we plan to use your stylesheet and the link(s) to the
data at the three ESGF locations are not implemented, yet. We filled the
page with our CERA test data.
We suggest to put the summary on the page, because otherwise there is no
immediate information available. The summary uses sentences from the
CMIP5 page and the experiment description of the questionnaire (atomfeed
experiment).
What is missing:
- construction of the link into the CIM repository to the simulationRun
document to replace the cirrus-link.
- datanode TDS root catalogue and file server root access for the data
access link.
- style sheet of your primary DOI target page.
To construct a link to the data at BADC and PCMDI we need the TDS root
and the file server root addresses. We plan to provide lists of chunks
for the given DOI and a list of ESG dataset links.
E.g. DKRZ:
tds root (replicated data): <a class="moz-txt-link-freetext" href="http://BLOCKEDbmbf-ipcc-ar5.dkrz.de/thredds/esgcet/1/">http://BLOCKEDbmbf-ipcc-ar5.dkrz.de/thredds/esgcet/1/</a>
fileserver root: <a class="moz-txt-link-freetext" href="http://BLOCKEDbmbf-ipcc-ar5.dkrz.de/thredds/fileServer/new/">http://BLOCKEDbmbf-ipcc-ar5.dkrz.de/thredds/fileServer/new/</a>
Please add your information for BADC and PCMDI at
<a class="moz-txt-link-freetext" href="http://BLOCKEDesgf.org/wiki/Cmip5Status">http://BLOCKEDesgf.org/wiki/Cmip5Status</a> .
Just to make sure: You will use one root for all replicated data? If
not, we cannot provide the link list but only the DRS names (TDS file_id
+ version + variable in case of chunks and TDS dataset_id in case of ESG
datasets).
What do you think? Any suggestions for improvements?
Any suggestions what the DOI service should provide for the users / the
portals? The chunk list for a DRS experiment will include hundreds of
links, which is not very convenient for the user.
Best wishes,
Martina
</pre>
</blockquote>
</body>
</html>