[Esip-documentation] ACDD questions

Ted Habermann thabermann at hdfgroup.org
Mon May 6 09:45:09 EDT 2013 

Nan et al.,

This is the current standard list with definitions… 

Remember that communities can 1) decide how they will use these standard codes, i.e. what the codes mean in their context, and 2) extend the code list if necessary. 

Take a look at the roles discussion in the talk page on the ESIP wiki. 

My tendency these days, in ISOLand, is towards not worrying to much about most of the role codes. In most cases the context of the CI_ResponsibleParty makes it clear what the organization/person does and the role pointOfContact works well. Unfortunately, in the current model for ACDD, that context does not exist, so role codes are probably more important. They actually support the process of translation to the proper ISO context.

I suspect most users don't really care what most role codes are. They are interested in someone to email. Whether that person is called distributor, publisher, or pointOfContact probably doesn't really matter.

In the resource citation, where attribution is more important, the roles probably still have a role.

Ted



 

Concept name (English)

Code

Definition

1.       

CI_RoleCode

 

function performed by the responsible party

2.       

resourceProvider

resourceProvider

party that supplies the resource

3.       

custodian

custodian

party that accepts accountability and responsibility for the resource and ensures appropriate care and maintenance of the resource

4.       

owner

owner

party that owns the resource

5.       

user

user

party who uses the resource

6.       

distributor

distributor

party who distributes the resource

7.       

originator

originator

party who created the resource

8.       

pointOfContact

pointOfContact

party who can be contacted for acquiring knowledge about or acquisition of the resource

9.       

principalInvestigator

principalInvestigator

key party responsible for gathering information and conducting research

10.     

processor

processor

party who has processed the data in a manner such that the resource has been modified

11.     

publisher

publisher

party who published the resource

12.     

author

author

party who authored the resource

13.     

sponsor

sponsor

party who speaks for the resource

14.     

coAuthor

coAuthor

party who jointly authors the resource

15.     

collaborator

collaborator

party who assists with the generation of the resource other than the principal investigator

16.     

editor

editor

party who reviewed or modified the resource to improve the content

17.     

mediator

mediator

a class of entity that mediates access to the resource and for whom the resource is intended or useful

18.     

rightsHolder

rightsHolder

party owning or managing rights over the resource

19.     

contributor

contributor

party contributing to the resource

20.     

funder

funder

party providing monetary support for the resource

21.     

stakeholder

stakeholder

party who has an interest in the resource or the use of the resource



==== Ted Habermann ===========================
   Director of Earth Science, The HDF Group
   New phone#: (217) 531-4202
   New email: thabermann at hdfgroup.org
==== thabermann at hdfgroup.org ==================

On May 6, 2013, at 7:58 AM, Nan Galbraith <ngalbraith at whoi.edu> wrote:

> Ted, can you tell us where the new ISO role codes can be found?
> 
> There's a list on the 'ISO People' wiki page you linked below, but I'm
> not sure if that's the complete list, and there are no definitions there.
> 
> I'm still not sure what a data publisher is, or how/if an owner differs
> from an originator or from an author. 
> 
> Thanks - Nan
> 
> 
> 
> On 4/26/13 2:30 PM, Ted Habermann wrote:
>> John et al.,
>> 
>> I agree completely that a shared vocabulary with definition is critical. The old ISO vocab is at https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19115_and_19115-2_CodeList_Dictionaries#CI_RoleCode. Many new roles were added in the most recent revision. There is also a brief discussion at http://wiki.esipfed.org/index.php/ISO_People (I will update that list to include revisions)...
>> 
>> What is really important is that the representation allow specification of the source of the code along with the code itself. This is possible in THREDDS, but not ACDD. The job of the standard is to say we use a codelist for this item and that codelist has a location. It is the communities job to say: this is the codelist that our community uses.
>> 
>> Ted
>> 
>> 
>> 
>> 
>> On Apr 26, 2013, at 1:02 PM, John Graybeal <graybeal at marinemetadata.org> wrote:
>> 
>>> Should be from a controlled vocabulary IMHO. BODC has (for SeaDataNet) an extension of ISO role terms, if I recall correctly. I think it isn't just for contributor roles, it's for all roles that this is needed—ISO wasn't very thorough in the first place, but there will always be new ways for people to be connected to a data set.  
>>> 
>>> I don't think we have to be restrictive (in what roles are allowed) but I think we should try to be explicit (about what a role means).
>>> 
>>> John
>>> 
>>> 
>>> On Apr 26, 2013, at 10:57, Nan Galbraith <ngalbraith at whoi.edu> wrote:
>>> 
>>>> Hi John -
>>>> 
>>>> One other item that I think we might need to have - beyond better definitions
>>>> for some of the existing terms -  is a CV for contributor roles. I think one exists,
>>>> somewhere, but I'm not sure where. BODC, maybe? MMI? Or should this really
>>>> be free text?
>>>> 
>>>> Thanks -
>>>> Nan
>>>> 
>>>> On 4/26/13 12:51 PM, John Graybeal wrote:
>>>>> Sorry for the noise. I pasted the wrong URL, meant to paste
>>>>>   https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery
>>>>> as my target space for work. Let me know if that doesn't make sense.
>>>>> 
>>>>> Thank you all for your advice about logging in on ESIP Fed.  I'm getting there…
>>>>> 
>>>>> John
>>>>> 
>>>>> ...
>>>>> 
> 
> -- 
> *******************************************************
> * Nan Galbraith        Information Systems Specialist *
> * Upper Ocean Processes Group            Mail Stop 29 *
> * Woods Hole Oceanographic Institution                *
> * Woods Hole, MA 02543                 (508) 289-2444 *
> *******************************************************
> 
> 
> _______________________________________________
> Esip-documentation mailing list
> Esip-documentation at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-documentation

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-documentation/attachments/20130506/45a50393/attachment-0001.html>

More information about the Esip-documentation mailing list