Suggested schema change
The vocabulary for name part types only has options for the name parts of person names. There are none for the name parts of group names. Group names can contain an inherent structure and EAC-CPF (the exchange schema used for exchange of party information between some of our partners and the NLA) supports name parts for corporate names

Problem this suggestion addresses
Corporate names may include multiple parts—for example, Monash University, Faculty of Engineering. Name parts to express the hierarchy of these names are required.
Note that this is a separate issue from using relatedObject relations to describe relationships between entities. This suggestion is to support better display of group names.
When we harvest records for research groups and insitutions from the NLA, the EAC-CPF record is mapped to an NLA party record. The name types they accept their records are:
parent, child, subordinate, superior
EAC-CPF example:
<entityId>http://nla.gov.au/anbd.aut-an36510507</entityId>
<entityType>corporateBody</entityType>
<nameEntry>

<part localType="superior”>CSIRO</part>
<part localType="subordinate">Division of Environmental Mechanics</part>
<authorizedForm>AACR2</authorizedForm>

</nameEntry>

If we supported these types for name parts also this would translate to:

<party type="group">

<identifier type="AU-ANL:PEAU">http://nla.gov.au/nla.party-627797</identifier>

<name type="primary">

<namePart type="superior">CSIRO</namePart>
<namePart type="subordinate">Division of Environmental Mechanics</namePart>
</name>

</party>


Identified by
Basil Dewhurst, manager of the NLA’s ARDC Party Infrastructure Project with ANDS

RIF-CS schema components affected
Vocabulary for namePart type.

Impact on content providers
None if namePart type remains optional for groups.

Pros
Better display of names for research groups such as faculties, departments, centres, divisions, branches.

Cons
Research Data Australia will need modification to exploit this extra information.

Technical options
The vocabulary terms “parent”, “child”, “subordinate” and “superior” will need to be added to the ORCA registry “tbl_terms” database table.
The vocabs.xml file will need to be amended to add the vocab namePart types “parent”, “child”, “subordinate” and “superior” definitions.
The vocabularies.html will need to be regenerated to reflect the addition of the namePart types “parent”, “child”, “subordinate” and “superior”.
Changes will be required to the content providers guide.

Proposal revised by:
--changing institution names in examples
--noting RIF-CS Advisory Board recommendation for which type labels should be used.


This revised proposal requires no action. It is provided only as a document of record.