Editing SV Community Roles

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 47: Line 47:
 
The behaviours of the data acquisition community is described at [[SV Community Behaviours|'''Acquisition Behaviours''']].
 
The behaviours of the data acquisition community is described at [[SV Community Behaviours|'''Acquisition Behaviours''']].
  
−
== <span id="RolesintheDataCurationCommunity">Roles in the Data Curation Community</span> ==
+
== <span id="ResearchInfrastructure#RolesintheDataCurationCommunity">Roles in the Data Curation Community</span> ==
  
 
The data curation community responds to provide quality data products and maintain the data resources. Consider a typical data curation scenario: when data is being imported into a curation subsystem, a ''curator'' will perform the quality checking of the scientific data. Unique identifiers will be assigned to the qualified data, which will then be properly catalogued by associating necessary metadata, and stored or archived. The main human roles interacting with or maintaining a data curation subsystem are ''data curators'' who manage the data and ''storage administrators'' who manage the storage facilities. Upon registering a digital object in a repository, its ''persistent identifier (PID)'' and the ''repository'' name or IP address is registered with a globally available system of ''identification services (PID service)''. Users may subsequently present the ''PID'' to an ''PID service'' to learn the network names or addresses of repositories in which the corresponding digital object is stored. Here, we use a more general term "PID" instead of ''"handle"'', and identify the key roles involved in the data curation process.
 
The data curation community responds to provide quality data products and maintain the data resources. Consider a typical data curation scenario: when data is being imported into a curation subsystem, a ''curator'' will perform the quality checking of the scientific data. Unique identifiers will be assigned to the qualified data, which will then be properly catalogued by associating necessary metadata, and stored or archived. The main human roles interacting with or maintaining a data curation subsystem are ''data curators'' who manage the data and ''storage administrators'' who manage the storage facilities. Upon registering a digital object in a repository, its ''persistent identifier (PID)'' and the ''repository'' name or IP address is registered with a globally available system of ''identification services (PID service)''. Users may subsequently present the ''PID'' to an ''PID service'' to learn the network names or addresses of repositories in which the corresponding digital object is stored. Here, we use a more general term "PID" instead of ''"handle"'', and identify the key roles involved in the data curation process.

Please note that all contributions to may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Copyrights for details). Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)