What does the RDA Toolkit include?RDA instructions (searchable and browseable)Views of RDA content by table of contents and by RDA element setAACR2 Rule Number Search of RDA instructionsWorkflows, mappings, examplesFull text of AACR2 with links to RDA
Can be purchased at ALA StoreAvailable in loose-leaf format
E-R models define entities, list their attributes, and identify relationships between entities
The FRBR user tasks are: to find entities that correspond to the user's search criteria , to identify an entity (i.e., to confirm that the entity described corresponds to the entity sought, or to distinguish between two or more entities with similar characteristics) , to select an entity that is appropriate to the user's needs (i.e., to choose an entity that meets the user's requirements with respect to content, physical format, etc....), and to acquire or obtain access to the entity described (i.e. to acquire an entity through purchase, loan, etc., or to access an entity electronically...)
The FRBR user tasks are: to find entities that correspond to the user's search criteria , to identify an entity (i.e., to confirm that the entity described corresponds to the entity sought, or to distinguish between two or more entities with similar characteristics) , to select an entity that is appropriate to the user's needs (i.e., to choose an entity that meets the user's requirements with respect to content, physical format, etc....), and to acquire or obtain access to the entity described (i.e. to acquire an entity through purchase, loan, etc., or to access an entity electronically...)
The FRBR user tasks are: to find entities that correspond to the user's search criteria , to identify an entity (i.e., to confirm that the entity described corresponds to the entity sought, or to distinguish between two or more entities with similar characteristics) , to select an entity that is appropriate to the user's needs (i.e., to choose an entity that meets the user's requirements with respect to content, physical format, etc....), and to acquire or obtain access to the entity described (i.e. to acquire an entity through purchase, loan, etc., or to access an entity electronically...)
The user tasks in FRAD are: find entities corresponding to stated criteria, identify an entity as being the one sought (or validate the form of name to be used for a controlled access point), contextualize (or place a person, corporate body, etc., in context – clarify the relationship between two or more of them), and justify the authority data creator’s reason for choosing the name or form of name on which an access point is based. The draft of RDA uses clarify and understand instead of contextualize and justify, but I believe this will be changed when the final version is released.
The user tasks in FRAD are: find entities corresponding to stated criteria, identify an entity as being the one sought (or validate the form of name to be used for a controlled access point), contextualize (or place a person, corporate body, etc., in context – clarify the relationship between two or more of them), and justify the authority data creator’s reason for choosing the name or form of name on which an access point is based. The draft of RDA uses clarify and understand instead of contextualize and justify, but I believe this will be changed when the final version is released.
RDA will also have several appendices that deal with things like capitalization, abbreviations, and an appendix of examples.
Core elements are similar to, but different from, AACR2 levels of description.