http://mediawiki.envri.eu/index.php?title=Identification_and_citation_in_SEADATANET&feed=atom&action=historyIdentification and citation in SEADATANET - Revision history2024-03-28T17:01:42ZRevision history for this page on the wikiMediaWiki 1.31.0http://mediawiki.envri.eu/index.php?title=Identification_and_citation_in_SEADATANET&diff=594&oldid=prevENVRIwiki: Created page with "== <span style="color: #BBCE00"> Context of identification and citation in SEADATANET</span>== == <span style="color: #BBCE00"> Summary of SEADATANET requirements for identif..."2020-03-31T16:39:09Z<p>Created page with "== <span style="color: #BBCE00"> Context of identification and citation in SEADATANET</span>== == <span style="color: #BBCE00"> Summary of SEADATANET requirements for identif..."</p>
<p><b>New page</b></p><div>== <span style="color: #BBCE00"> Context of identification and citation in SEADATANET</span>==<br />
<br />
== <span style="color: #BBCE00"> Summary of SEADATANET requirements for identification and citation</span>==<br />
<br />
== <span style="color: #BBCE00"> Detailed requirements</span>==<br />
<br />
=== <span style="color: #BBCE00">IDENTIFICATION </span> ===<br />
<br />
# <span style="color: #BBCE00">What granularity do your RI’s data products have:</span> <br> '''<span style="color: #BBCE00">a) Content-wise (all parameters together, or separated e.g. by measurement category)?</span>''' <br> Products gather parameter category, e.g. temperature and salinity of the water column are in a single product. Observation data sets also managed by the infrastructure are managed individually per sampling features (e.g. vertical profile, time series, trajectories, …), per observing platform. <br> <span style="color: #BBCE00">b) Temporally (yearly, monthly, daily, or other)?</span> <br> Seadatanet provides compilation of data sets over decades for climatological study purpose. <br> <span style="color: #BBCE00">c) Spatially (by measurement station, region, country or all together)?</span> <br> The products group observations spatially, by sea basin (e.g. Black Sea, Baltic Sea, Arctic Ocean, North Atlantic Ocean, ...)<br />
# '''How are the data products of your RI stored - as separate “static” files, in a database system, or a combination?''' <br> The products are separated static files. The input observations also managed by the infrastructure are managed heterogenously in databases or files. The harmonization is done thanks to web services on top of the datasets.<br />
# <span style="color: #BBCE00">How does your RI treat the “versioning” of data - are older datasets simply replaced by updates, or are several versions kept accessible in parallel?</span> <br> For product version is managed (DOI are minted). For observation only the best (latest) copy is managed.<br />
# <span style="color: #BBCE00">Is it important to your data users that</span> <br> <span style="color: #BBCE00">a) Every digital data object is tagged with a unique & persistent digital identifier (PID)?</span> <br> Yes <br> <span style="color: #BBCE00">b) The metadata for data files contains checksum information for the objects?</span> <br> Yes if it enables to detect quality control updates in the dataset. <br> <span style="color: #BBCE00">c) Metadata (including any documentation about the data object contents) is given its own persistent identifier?</span> <br> No <br> <span style="color: #BBCE00">d) Metadata and data objects can be linked persistently by means of PIDs?</span> <br> Yes<br />
# <span style="color: #BBCE00">Is your RI currently using, or planning to use, a standardized system based on persistent digital identifiers (PIDs) for:</span> <br> <span style="color: #BBCE00">a) “Raw” sensor data?</span> <br> A central system called Common Data Index (CDI) delivers identifiers for observations. However the identifier is delivered 3 to 5 years after observation is done. Local identifiers are also used by the data centres of the network. We are looking into using UUID for observations or observing platforms. If one UUID is associated with each platform, then the identification of observations dataset is going to be eased. We are looking into OGC/PUCK standard interfaces to get these unique identifiers. <br> <span style="color: #BBCE00">b) Physical samples?</span> <br> IGSN is sometimes used for geological sampling. <br> <span style="color: #BBCE00">c) Data undergoing processing (QA/QC etc.)?</span> <br> No <br> <span style="color: #BBCE00">d) Finalized “publishable” data?</span> <br> Yes product have UUID and DOIs<br />
# <span style="color: #BBCE00">Please indicate the kind of identifier system that are you using - e.g. Handle-based (EPIC or DOI), UUIDs or your own RI-specific system?</span> <br> See above<br />
# <span style="color: #BBCE00">If you are using Handle-based PIDs, are these handles pointing to “landing pages”? Are these pages maintained by your RI or an external organization (like the data centre used for archiving)?</span> <br> DataCite DOIs are defined after automated UUID, for example: http://dx.doi.org/10.12770/2a5c1396-f832-4500-8faa-8cfeeded1ebb<br />
# <span style="color: #BBCE00">Are costs associated with PID allocation and maintenance (of landing pages etc.) specified in your RI’s operational cost budget?</span> <br> No, cost are shared by differents infrastructures and small regaring the overall budget. <br> <br />
<br />
=== <span style="color: #BBCE00">CITATION</span> ===<br />
<br />
# '''How does your “designated scientific community” (typical data users) primarily use your data products? As input for modelling, or for comparisons?''' <br> Comparison, local study<br />
# '''Do your primary user community traditionally refer to datasets they use in publications:''' <br> <span style="color: #BBCE00">a) By providing information about producer, year, report number if available, title or short description in the running text (e.g. under Materials and Methods)?</span> <br>-- <br> <span style="color: #BBCE00">b) By adding information about producer, year, report number if available, title or short description in the References section? </span> <br> -- <br> <span style="color: #BBCE00">c) By DOIs, if available, in the References section?</span><br> Would like to push for using DOIs.<br><span style="color: #BBCE00">d) By using other information?</span> <br>--<br />
# <span style="color: #BBCE00">Is it important to your data users to be able to refer to specific subsets of the data sets in their citation? Examples:</span> <br> <span style="color: #BBCE00">a) Date and time intervals</span> <br> <span style="color: #BBCE00">b) Geographic selection</span> <br> <span style="color: #BBCE00">c) Specific parameters or observables</span> <br> For SeaDatNet strictly speaking the priority is to enalbe citation of the whole datasets which is static. If we extend the scope to marine data management, subsetting is important (x,y,t, observed properties) but, in case of citation, no as much as snapshot tag, or quality assessment method applied to dataset which can evolve continuously. There is a challenge to improve this.<br />
# <span style="color: #BBCE00">Is it important to be able to refer to many separate datasets in a collective way, e.g. having a collection of “all data” from your RI represented by one single DOI?</span> <br> Datasets are compiled together in a specific process to harmonized data for specific usage (e.g. cliamtology). Then the product is cited and has its own DOI. Not a priority to cite on-demand compilation yet.<br />
# <span style="color: #BBCE00">What strategy does your RI have for collecting information about the usage of your data products?</span> <br> <span style="color: #BBCE00">a) Downloads/access Authentication of data access (user directory).</span> <br> Log analysis. <br> <span style="color: #BBCE00">b) Visualization at your own data portal.</span> <br> Non authenticated Log analysis <br> <span style="color: #BBCE00">c) Visualization at other data portals</span> <br> Non authenticated. Log and refererer analysis <br> <span style="color: #BBCE00">d) References in scientific literature</span> <br> “Manual” survey done with the support a library team. <br> <span style="color: #BBCE00">e) References in non-scientific literature</span> <br> “Manual” survey done with the support a library team. <br> <span style="color: #BBCE00">f) Scientific “impact”</span> <br> “Manual” survey done with the support a library team.<br />
# <span style="color: #BBCE00">Who receives credit when a data set from your RI is cited?</span> <br> Hereafter is what should be done, not what is available <br> <span style="color: #BBCE00">a) The RI itself</span> <br> yes <br> <span style="color: #BBCE00">b) The RI’s institutional partners (all or in part, depending on the data set contents)</span> <br> yes, with weight or specific feedback (dashboards) related to the contribution of each. <br> <span style="color: #BBCE00">c) Experts in the RI’s organization (named individuals)</span> <br> no (data managers or IT experts should be transparent, neutral in the process of data delivery) <br> <span style="color: #BBCE00">d) “Principal investigators” in charge of measurements or data processing (named individuals)</span> <br> yes, they are the one contributing to the RI by providing data <br> <span style="color: #BBCE00">e) Staff (scientists, research engineers etc.) performing the measurements or data processing (named individuals)</span> <br> yes, they are the one contributing to the RI by providing data<br />
# <span style="color: #BBCE00">What steps in tooling, automation and presentation do you consider necessary to improve take up of identification and citation facilities and to reduce the effort required for supporting those activities?</span> <br> Standardisation of data citation by the publishers. (on-going) Develop a full framework from user registration to usage analysis (download, view) via proper business oriented activity log and “customer relationship management”.<br />
<br />
== <span style="color: #BBCE00"> Formalities (who & when) </span>==<br />
<br />
{| class="wikitable"<br />
|-<br />
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Go-between</span>'''</div><br />
| ?? <br> Info added by topic coordinator Maggie Hellström<br />
|-<br />
! <div style='text-align: left;'>'''<span style="color: #BBCE00">RI representative</span>'''</div><br />
| ??<br />
|-<br />
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Period of requirements collection</span>'''</div><br />
| Nov 2015 - December 2015<br />
|-<br />
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Status</span>'''</div><br />
| Requirements collection completed<br />
|}<br />
<br />
[[Category:Topic requirements by RI (detailed)]]</div>ENVRIwiki