1. Department of Information Sciences, University of Zadar, Croatia
Name Authority Data Interoperability Conceptual Model FRAD and ISAAR(CPF)
Mirna Willer
Department of Information Sciences, University of Zadar, Croatia
11/20/2018
RAMS, Zadar, May, 2013

2. Why the topic?
Interoperability may be justified by the need of the two communities to share, build and re-use professionally and work-intensively produced, authentic and reliable name authority data in current systems, and in the Semantic Web.
This will also enhance resource discovery, as the control over authorized data proves to be ever more important in the web environment where AAA (Anybody can say Anything about Anything) is a rule.
11/20/2018
RAMS, Zadar, May, 2013

3. Is it methodologically correct...?
Is it methodologically correct to “compare/map” a conceptual model – FRAD, and a standard – ISAAR(CPF) stipulating the structure and the content of a finding aid?
11/20/2018
RAMS, Zadar, May, 2013

4. IFLA / ICA/CDS Activities and publications
1992
1993
1995
1996
1998
1999
2000
2001
2003
2004
2009
2011
2012
IFLA FRBR WG ( ); FRBR: final study, 1998
ICA ISAAR(CPF) rev. ( ); ISAAR(CPF), 1st ed., 1996
IFLA & ICA Congress, Beijing
IFLA, WG on MLAR and the ISADN ( ); Minimal Level [etc.], 1998
ICA/CDS: ISAAR(CPF) & MLAR comparison
IFLA WG on FRANAR ( ); FRAD: conceptual model, 2009
ICA/CDS, ISAAR(CPF) revision ( ); ISAAR(CPF), 2nd ed., 2004
IFLA WG FRANAR, on ISAAR, 1st ed.
IFLA WG FRANAR, on ISAAR, draft, 2nd ed. Dialogue
FRAD, errata
IFLA FRBR RG: 2011-consolidation of models
ICA/CBPS: harmonization; ICA/AtoM
11/20/2018
RAMS, Zadar, May, 2013

5. IFLA, FRBR & MLAR: Universal Bibliographic Control
Functional Requirements for Bibliographic Records (1998)
Entities: persons, corporate bodies
Mandatory Elements for Internationally Shared Resource Authority Records (1998)
IFLA goal of Universal Bibliographic Control by way of requiring everyone to use the same form for headings globally is not practical
allowing the preservation of national or rule-based differences in authorized forms for headings to be used in national bibliographies and library catalogues that best meet the language and cultural needs of the particular institution's users
11/20/2018
RAMS, Zadar, May, 2013

6. The Internal Standard Archival Authority Record for Corporate Bodies, Persons and Families (ICA) and the Essential Data Elements for Internationally Shared Resource Authority Records (IFLA): A Comparison and Report (1998)
The centrality of provenance as a defining characteristic of archival materials means that archival authority files must include substantive information about the creators of the records vs. the librarian’s emphasis on an economical method of headings control
archival authority records share many data elements in common with their bibliographic counterparts. However, archival authority files are intended to serve a broader function than is envisioned for library authority data and therefore will be more detailed in their content.
In answering the vital question “can archivists adopt the IFLA model on authority records as theirs,” the answer is YES, but with certain conditions
11/20/2018
RAMS, Zadar, May, 2013

7. FRAD Entities: Person, Corporate Body, Family
Working Group on Functional Requirements And Numbering of Authority Records (FRANAR) ( )
FRAD Entities: Person, Corporate Body, Family
Comments on ISAAR(CPF), 1st ed (2001) & Draft 2nd ed. (2003)
WG on FRANAR to ICA/CDS (2003): Continuing the Dialogue
“an interest in our suggestion that it might be possible to develop some sort of a common statement for archives and libraries on authority records”
T. Delsey, consultant to WG on FRANAR: Cross-Sector Sharing of Authority Data (section from FRANAR, Draft)
11/20/2018
RAMS, Zadar, May, 2013

8. T. Delsey: there is potential for cross-sector sharing of authority data; however ...
the model may be applicable to those other sectors; however, there are functions and practices unique to each sector ... Nonetheless, the library model in itself does serve to highlight certain structural elements that may complicate cross-sector data transfer.
the authority files created by archives centre on entities referred to as persons, families, and corporate bodies, it is unlikely that those entity types as defined in an archival context would parallel directly the similarly named entities in the library model: concepts such as “bibliographic identity”...
one individual would be recognized as two or more persons
the archival authority record is likely to have been created for use with all documents associated with that body throughout the course of its existence as a legal entity. The library, on the other hand, may require two or more records, each representing the body during the specific period at which it used a particular form of name (not necessarily its legal name) to identify itself in its publications
authorized heading established for the archival authority record may or may not be directly transferable to one of the library authority records, depending on whether or not the form and structure of the heading is consistent with the rules governing headings created for the library authority file
11/20/2018
RAMS, Zadar, May, 2013

9. ISAAR(CPF), 2004: Scope and Purpose
1.5 There are many reasons why separate capture and maintenance of this type of contextual information is a vital component of archival description. [...] enables the linking of descriptions of records creators and contextual information to descriptions of records from the same creator(s) that may be held by more than one repository and to descriptions of other resources such as library and museum materials that relate to the entity in question. 1.8 Archival authority records are similar to library authority records in as much as both forms of authority record need to support the creation of standardized access points in descriptions. 1.9 Archival authority records, however, need to support a much wider set of requirements than is the case with library authority records. [...] archival authority records go much further and usually will contain much more information than library authority records.
11/20/2018
RAMS, Zadar, May, 2013

10. What did I do?
11/20/2018
RAMS, Zadar, May, 2013

11. Documents
IFLA. Functional Requirements for Authority Data (FRAD) by IFLA Working Group on Functional Requirements and Numbering of Authority Records (FRANAR), 2009; Errata (2011)
ICA. ISAAR(CPF), 2nd ed., 2004.
ICA, CBPS, Sub-committee on archival description. Progress report for revising and harmonising ICA descriptive standards, 4 July 2012,
ICA-AtoM's architecture, 2012,
Salvatore Vassallo, Creative Commons Attribution 3.0, FRAD – ISAAR(CPF) – EAC/CPF – Topic Maps Mapping,
11/20/2018
RAMS, Zadar, May, 2013

12. Focus on ... as an example
FRAD: Bibliographic Universe  “bibliographic identity” vs. ISAAR(CPF): Real-world entities
Functions and practices: [NO]
Entities and their definitions: Person
Form and Structure of Access points – Attributes / Description Area: [NO]
Relationships
11/20/2018
RAMS, Zadar, May, 2013

13. 11/20/2018
RAMS, Zadar, May, 2013

14. (Controlled) Access Point
ENTITY / Definition
FRAD
ISAAR(CPF)
Person
An individual or a persona or identity established or adopted by an individual or group. %
Family
Two or more persons related by birth, marriage, adoption, civil union, or similar legal status, or who otherwise present themselves as a family.
Corporate Body
An organization or group of persons and/or organizations identified by a particular name acting as a unit.
An organization or group of persons that is identified by a particular name and that acts, or may act, as an entity. Also includes an individual acting in a corporate capacity.
(Controlled) Access Point
A name, term, code, etc., under which a bibliographic or authority record or reference will be found.
A name, term, keyword, phrase or code that may be used to search, identify and locate archival descriptions, including authority records.
11/20/2018
RAMS, Zadar, May, 2013

15. FRAD relationships:
Relationships between primary entity types: generic level
[Bibliographic Entities] has appellation (known by) [Names] / is appelation of
[Names] is basis for [Controlled Access Point] / is based on
11/20/2018
RAMS, Zadar, May, 2013

16. (2) Relationships between specific instances of the entities: Persons, Families, Corporate Bodies,...
Type of Relationship
FRAD
ISAAR(CPF)
Person↔Person
pseudonymous
Not a relationship. In
ISAAR pseudonyms are in 5.1.5
other forms of name
[real name]
authorized form of name
secular
religious
official
attributive %
collaborative
ISAAR relationships, 5.3.2
associative
sibling
family
parent/child
family (or hierarchical)
11/20/2018
RAMS, Zadar, May, 2013

17. (3) Relationships between specific instances of the entity and name: various names of Persons, ...
Type of Relationship
FRAD
ISAAR(CPF)
Name of Person↔Name of Person
earlier name
other forms of name
temporal (predecessor/successor)
later name
alternative linguistic form
parallel forms of name
other variant name
11/20/2018
RAMS, Zadar, May, 2013

18. (4) Relationships between specific instances of the entity controlled access point
Type of relationship
FRAD
ISAAR(CPF)
Controlled Access Point ↔ Controlled Access Point
parallel language
parallel forms of name
alternate script
different rules
standardized forms according to other rules
11/20/2018
RAMS, Zadar, May, 2013

19. ... Only a tip of the iceberg: needs further research, preferably in the context of the Semantic Web and Linked Open Data concepts....
11/20/2018
RAMS, Zadar, May, 2013