Are there prerequisites for joining BIBCO?

Yes, independence in NACO name and name-title records, preferably through the NACO-Music Project is a prerequisite.  It may be possible for NACO and BIBCO review to occur simultaneously.

If a current BIBCO library or individual catalogers at a BIBCO library join the Music funnel, will they then report statistics for music records through the funnel?

As of 2018, the PCC collects statistics through its Directory. Each participating BIBCO cataloger reports their statistics to the PCC either through their institutional BIBCO liaison (if their institution is a full-level BIBCO member), or through their own PCC Directory login (if their institution is a funnel-level BIBCO member). Additionally, the BIBCO Music Funnel Coordinator collects format-specific statistics through a semi-annual survey; all music BIBCO record contributors are encouraged to submit statistic through this mechanism, regardless of their PCC reporting mechanism.

Will current BIBCO members who are already contributing music records need to be reviewed again to become members of the funnel?

No, current independent members remain so and will continue to contribute records in the same manner as before. They will also continue to be able to train new BIBCO catalogers at their own institutions with no intervention from the funnel. If an institution joins the funnel, their participating catalogers will be listed in the BIBCO Music Funnel directory of members, and they may join the BIBCO Music Funnel listserv. They may also volunteer to serve as reviewers for new members from other institutions.  

Does joining the BIBCO Music Funnel mean that the institution will have a funnel-level membership in BIBCO?

Joining a subject-specific funnel means that the members are part of a community of subject specialists who work together to create high quality bibliographic records that meet the standards of the BIBCO Standard Record (BSR). The BIBCO program has two levels of membership, full and funnel, and institutions may have either type of membership and still also be a part of a subject-specific funnel. In other words, belonging to a funnel and having a funnel-level BIBCO membership are not synonymous. Either an individual or an institution may complete an application to be part of the funnel.

Which authorized access points (AAPs) in score and sound recording BIBCO records must be backed by authority records?

The BIBCO Participants Manual (BPM) and the BIBCO Standard Record Metadata Application Profile (BSR MAP) both address the requirement that authorized access points (AAPs) in BIBCO records should be backed by authority records in the LC Name Authority File (hereafter referred to as NARs). However, these documents gloss over certain nuances commonly encountered in music cataloging that this FAQ describes in more detail. The BSR MAP states only that “Authority records must support authorized access points in a BIBCO record.” The BPM, specifically sections E5.2 and E5.3, gives some additional guidance, but E5.3 acknowledges that not all work and expression AAPs must necessarily be backed by authority records. It only states that:

“According to LC Descriptive Cataloging Manual Z1 (DCM Z1), Introduction, authority records for works and expressions are often made when:

      • a reference will be provided on that authority record; or,
      • research done to establish that authorized access point must be recorded; or, 
      • the authorized access point is needed for a related work access point or subject entry, and the related work is not represented by a bibliographic record in the LC database, or, for serials, by a CONSER record in OCLC; or,
      • certain information needs to be recorded, e.g., citation title for a law. 

“However, BIBCO catalogers may create authority records for any work or expression access points that they need in their cataloging, even if they do not fall into the categories listed above.”

This FAQ attempts to rectify this seeming contradiction in BIBCO documentation. 

The specific guidance below represents the BIBCO Music Funnel’s interpretation of BIBCO policy in a music context. Where future conflict may occur between this FAQ and official BIBCO documentation, the latter takes precedence. All newly-created NARs must be coded RDA. Pre-existing NARs should preferably be coded RDA or at least be determined to be RDA acceptable (as defined in the PCC Post [Original] RDA Test Guidelines). In BIBCO records:

    1. All person and corporate body AAPs (1xx/7xx fields without $t) must be backed by NARs.
    2. All series AAPs in 8xx fields must be backed by SARs (tracing series is optional).
    3. All work-level AAPs in a 1xx/240 field pair, in 730 fields, and in 700/710/711 fields with $t must be backed by NARs. This includes conventional collective titles, individual whole works, and parts of works (e.g., movements, arias).
      • When creating a NAR for a part of a work, a NAR for that whole work should also be created or recoded to RDA as needed.
      • Exception: for NARs for work-level AAPs for works that include “$k Selections,” the AAP for the work as a whole must be backed by a NAR, and an additional NAR based on this work’s AAP plus “$k Selections” may optionally be created. When deciding whether to create such NARs, consider the guidance cited above from DCM Z1. 
    4. The work portion (including subfields $t, $m, $n, $p, $r) of all expression-level AAPs in a 100/240 field pair and in 7xx fields must be backed by NARs. 
    5. Work-level AAPs represented by a 1xx/245 field pair may optionally be backed by a NAR; creating NARs for such situations is strongly encouraged.
      • Adding a 240 field that exactly matches 245 $a is optional, but when present, the work represented in the resulting 1xx/240 field pair must be backed by a NAR.
    6. Work- and expression-level AAPs in a 130 field may optionally be backed by a NAR, such as in cases where the cataloger determines that the bibliographic record itself does not sufficiently describe the work/expression or where catalogers wish to document additional research.
      • This interpretation is in alignment with CONSER practice, where NARs for serial works are not routinely created to back 130 fields in CONSER records.
    7. NARs for AAPs containing expression-level components (including subfields $f, $h, $l, $o, $s) may optionally be created. This includes AAPs representing classes of expressions (e.g., all arrangements of a given work) or individual expressions (noting that LC-PCC PS 6.28.3, LC Practice, discourages the formulation of unique expression AAPs).
      • When deciding whether to create a NAR for a class of expressions of a musical work, consider the guidance cited above from DCM Z1. For example, “research done to establish” often comes into play with ambiguous situations as to entity boundaries between works (adaptations) and expressions (arrangements). Documenting this research in a NAR that might not otherwise need to be created can save time for other catalogers confronting similar situations.
      • Another common example of a class-of-expression NAR is a work AAP (that includes a medium of performance statement in $m) followed by “;$o arranged”. The presence of this NAR allows catalogers to record one or more variant access points with arranged mediums of performance in $m. This helps other catalogers and end users by documenting in the authority file which mediums of performance are to be considered arrangements of a work and which mediums of performance are alternatives sanctioned by the composer. Example:

100 1_ Boccherini, Luigi, ǂd 1743-1805. ǂt Sonatas, ǂm violin, piano, ǂn G. 25-30; ǂo arranged

400 1_ Boccherini, Luigi, ǂd 1743-1805. ǂt Sonatas, ǂm flute, pedal harp, ǂn G. 25-30


100 1_ Boccherini, Luigi, ǂd 1743-1805. ǂt Sonatas, ǂm violin, piano, ǂn G. 25-30

400 1_ Boccherini, Luigi, ǂd 1743-1805. ǂt Sonatas, ǂm violin, harpsichord, ǂn G. 25-30