Functional Requirements for Authority Data
E308405
Functional Requirements for Authority Data is an IFLA conceptual model that defines the functions, entities, and relationships needed to support authority control in library and bibliographic information systems.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Functional Requirements for Subject Authority Data | 5 |
| Functional Requirements for Authority Data canonical | 4 |
How this entity was disambiguated
This entity first appeared as the object of triple T2900620 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: Functional Requirements for Authority Data Context triple: [Resource Description and Access, basedOn, Functional Requirements for Authority Data]
-
A.
Program for Cooperative Cataloging
The Program for Cooperative Cataloging is an international library initiative that coordinates shared cataloging standards and workflows to improve the quality and efficiency of bibliographic and authority records worldwide.
-
B.
MARC standards
MARC standards are a set of bibliographic data formats used worldwide to structure and exchange library catalog information in a consistent, machine-readable way.
-
C.
RDA
RDA (Resource Description and Access) is a modern international cataloguing standard used by libraries to describe and provide access to information resources in both digital and physical formats.
-
D.
Total Digital Access to the League of Nations Archives (LONTAD)
Total Digital Access to the League of Nations Archives (LONTAD) is a major initiative to preserve, digitize, and provide online access to the historical records of the League of Nations.
-
E.
Library of Congress authority record
A Library of Congress authority record is a standardized cataloging entry that establishes the authorized form of names, subjects, and titles to ensure consistent identification and retrieval of bibliographic information.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: Functional Requirements for Authority Data Target entity description: Functional Requirements for Authority Data is an IFLA conceptual model that defines the functions, entities, and relationships needed to support authority control in library and bibliographic information systems.
-
A.
Program for Cooperative Cataloging
The Program for Cooperative Cataloging is an international library initiative that coordinates shared cataloging standards and workflows to improve the quality and efficiency of bibliographic and authority records worldwide.
-
B.
MARC standards
MARC standards are a set of bibliographic data formats used worldwide to structure and exchange library catalog information in a consistent, machine-readable way.
-
C.
RDA
RDA (Resource Description and Access) is a modern international cataloguing standard used by libraries to describe and provide access to information resources in both digital and physical formats.
-
D.
Total Digital Access to the League of Nations Archives (LONTAD)
Total Digital Access to the League of Nations Archives (LONTAD) is a major initiative to preserve, digitize, and provide online access to the historical records of the League of Nations.
-
E.
Library of Congress authority record
A Library of Congress authority record is a standardized cataloging entry that establishes the authorized form of names, subjects, and titles to ensure consistent identification and retrieval of bibliographic information.
- F. None of above. chosen
Statements (55)
| Predicate | Object |
|---|---|
| instanceOf |
IFLA standard
ⓘ
conceptual model ⓘ |
| abbreviation |
FRAD
ⓘ
FRBR-related model ⓘ |
| appliesTo |
authority data
ⓘ
bibliographic information systems ⓘ library information systems ⓘ |
| basedOn | Functional Requirements for Bibliographic Records ⓘ |
| concernsEntityType |
concepts
ⓘ
corporate bodies ⓘ events ⓘ expressions ⓘ families ⓘ items ⓘ manifestations ⓘ objects ⓘ persons ⓘ places ⓘ works ⓘ |
| defines |
entities for authority data
ⓘ
functions for authority data ⓘ relationships for authority data ⓘ |
| field |
authority control
ⓘ
bibliographic control ⓘ library and information science ⓘ |
| focusesOn |
authority records
ⓘ
controlled access points ⓘ disambiguation of names ⓘ identification of entities ⓘ |
| hasComponent |
attributes of entities
ⓘ
relationships between entities ⓘ user tasks for authority data ⓘ |
| hasGoal |
improve access to bibliographic and authority data
ⓘ
support authority control ⓘ |
| hasUserTasks |
clarify
ⓘ
control ⓘ find ⓘ identify ⓘ understand ⓘ |
| influenced |
RDA
ⓘ
Resource Description and Access ⓘ authority data modeling practices ⓘ |
| publisher |
International Federation of Library Associations and Institutions
ⓘ
surface form:
IFLA
International Federation of Library Associations and Institutions ⓘ |
| relatedTo |
Functional Requirements for Bibliographic Records
ⓘ
surface form:
FRBR
FRSAD ⓘ Functional Requirements for Bibliographic Records ⓘ Functional Requirements for Authority Data self-linksurface differs ⓘ
surface form:
Functional Requirements for Subject Authority Data
|
| supports |
authority file design
ⓘ
cataloguing rules development ⓘ metadata schema design ⓘ user tasks in authority data ⓘ |
| usedBy |
authority file managers
ⓘ
bibliographic agencies ⓘ libraries ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: Functional Requirements for Authority Data Description of subject: Functional Requirements for Authority Data is an IFLA conceptual model that defines the functions, entities, and relationships needed to support authority control in library and bibliographic information systems.
Referenced by (9)
Full triples — surface form annotated when it differs from this entity's canonical label.