4.4.2 Request point of contact

Required	Repeatable
Yes	Yes

Definition:

The relevant point of contact for requesting access to the data asset (e.g. the data custodian). The point of contact should be enduring (e.g. role-based) as opposed to a specific individual (e.g. a chief investigator).

This may be a different point of contact than that used for enquiries about the data asset (see Enquiries (4.4.1)).

This field will be used by the HeSANDA Federations Service to direct where data requests will be sent.

The Request Point of Contact will need to be separately registered with ARDC to enable this functionality. To register, please provide the contributorName and associated email address to the HeSANDA team.

Metadata fields:

Example DataCite XML

<contributors>
    <contributor contributorType="Distributor">
        <contributorName xml:lang="en" nameType="Organizational">Australasian Leukaemia and Lymphoma Group (ALLG)</contributorName>
        <nameIdentifier schemeURI="https://ror.org/" nameIdentifierScheme="ROR">https://ror.org/05t72y326</nameIdentifier>
    </contributor>
</contributors>

DataCite 7.a contributorType 

Occurrences: 1

Input type: Text

Example input: Must be “Distributor”

Controlled vocabulary source:

Notes:

DataCite 7.1 contributorName 

Occurrences: 1

Input type: Text from list

Example input: Australasian Leukaemia and Lymphoma Group (ALLG)

Controlled vocabulary source: List of all HeSANDA data providers

Notes:

Since the system will be matching based on the contributorName, this field must be applied consistently.

DataCite 7.1.a nameType 

Occurrences: 1

Input type: Text from list

Example input: Must be “Organizational”

Controlled vocabulary source:

Notes:

DataCite 7.4 nameIdentifier 

Occurrences: 0-n

Input type: Text

Example input: https://ror.org/05t72y326

Controlled vocabulary source:

Notes: Go to https://ror.org/ to look up the ROR ID for an organisation.

DataCite 7.4.a nameIdentifierScheme 

Occurrences: 1

Definition: The name of the name identifier scheme.

Allowed values, examples, other constraints:

If nameIdentifier is used, nameIdentifierScheme is mandatory.

Examples:

ORCID
ISNI
ROR

DataCite 7.4.b schemeURI 

Occurrences: 0-1

Definition: The URI of the name identifier scheme.

Allowed values, examples, other constraints:

Examples:

DataCite 7.5 affiliation 

Occurrences: 0-n

Definition: The organizational or institutional affiliation of the contributor.

Allowed values, examples, other constraints

Free text.

The contributor’s nameType may be Organizational or Personal. In the case of an organizational contributor, e.g., a research group, this will often be the name of the institution to which that organization belongs.

Examples:

German National Library of Science and Technology
DataCite

DataCite 7.5.a affiliationIdentifier 

Occurrences: 0-1

Definition: Uniquely identifies the organizational affiliation of the contributor.

Allowed values, examples, other constraints:

The format is dependent upon scheme.

Examples:

DataCite 7.5.b affiliationIdentifierScheme 

Occurrences: 1

Definition: The name of the affiliation identifier scheme.

Allowed values, examples, other constraints:

If affiliationIdentifier is used, affiliationIdentifierScheme is mandatory.

Examples:

ROR
ISNI

DataCite 7.5.c schemeURI 

Occurrences: 0-1

Definition: URI of the affiliation identifier scheme.

Allowed values, examples, other constraints:

Examples: