SBTF Priority List

From SharedBib

Jump to: navigation, search

Contents

Shared Bib Task Force Draft Prioritization for FLVC 3-22-13

Priority List Categorized by Status

Projects of high priority already underway

  • Cleaning up MarcIt records to which OCLC numbers were incorrectly added during USF’s reclamation project and implementing regular monthly MarcIt loads for USF.
  • Continuing to update GenLoad in response to need; current priority is to revise it so that item records can be overlaid.
  • Completing work on Serials Solutions e-book loads for UF.
  • Completing work on implementing the monthly loads of Marcive government document records, including the loading of electronic-only records.
  • Completing the necessary changes to support RDA implementation in Aleph and Mango. RT: MAOD will create two tickets to track the Aleph and Mango changes separately.

Priorities that will enable the batch loading of records

  • Further Analysis/Discussion. Write a script to modify P_File_90 and GenLoad so that they can be set not to consider any bib with Discovery Record status to be a matching record.
  • RT: from each SUL. Do global changes to PDA bibs so that all PDA bibs have the status: Discovery Record.
  • Create Wiki Page to Track TOC Project - MOD. Do global changes to remove the status of DO NOT OFFLOAD on bibs with protected Tables of Contents and Summaries. (It now appears that historical TOCs will be purchased for all SULs. However, the on-going future collective acquisition of TOCs is unknown. If only some SULs purchase TOCs and summaries, FLVC needs to make sure that new batches of enriched bibs are marked with a specific status indicating that the bib contains proprietary fields but can otherwise be shared. Was wording for this status already chosen?)

Priorities that will standardize data and facilitate editing

  • Further Analysis/Discussion. Do global changes on ebrary records so that the ISBN is always in 020 $a. (Currently it is often in 020 $z.)
    • EHolmes will inquire with Ebrary. Going forward, require any library loading ebrary records to use MarcEdit to move any incorrectly subfielded ISBNs to 020 $a before loading.
    • EHolmes reported the Ebrary: will change the all or nothing for the $a.
  • Further Analysis/Discussion/Problematic. Mary Ann mentioned that the ISBN in Coutts records is often in an 024 field. Global changes should also be run on the Coutts records already loaded to move the ISBN to the 020 $a field and subfield; new records to be loaded should be edited in MarcEdit to correctly code the ISBN before the records are loaded.
  • Further Analysis/Discussion. Revise load programs so that fields which no longer need to be protected by $5 can be overlaid. (See Appendix III in Shared Bib Cataloging Guidelines.)

Priorities relating to Mango

  • Further Analysis/Discussion with FLVC Programmers: Change the Mango software so that it de-dups upon display; this function was built into pre-merge Mango and is still needed because of the numerous duplicate records in the merged database, which can be confusing to our users.
  • DAlsbury will create: Report of duplicate records with same OCLC number DONE
  • Further Analysis/Discussion - Report back from BCD:Fix the Mango display so that only 2nd indicator “0” of the 856 field will generate an e-icon. What we want to avoid is the display of an e-icon when correctly coded links (2nd indicator “1”) are added as a user service to print records for freely available online versions. (Currently the display is blocked by a stoplist of terms. This method was adopted because of widespread inconsistent coding of the 2nd indicator, particularly in older materials. Consequently, it may be necessary to continue the stoplist as an additional filter, but meanwhile only 2nd indicator “0” should generate an e-icon.)

Priorities relating to authority control that will make workflows more efficient and support facet display

  • Implement UPD Y: “UPD Y is an Aleph function in cataloging that supports the automatic updating of headings in bibliographic records to match the authorized form of the LC heading by changing the update code form “N=no” to “Y=yes” in the authority record.” (from Authorities Subcommittee White Paper).
    • Legacy Project: Implement UPD Y at the record-by-record level ("little UPD Y"). This is the one-off UPD Y implemenation where it's turned on at the single-record level.
    • On FLVC Project List 2013/14: Implement UPD Y for LCA10 as a whole ("big UPD Y"). This requires investigation of the impact on system resources of turning on UPD Y en masse.
  • Legacy Project: Allow LCA10 editing: LCA10 is the national authority file accessible via Aleph shared bib. With LCA10 editing permissions set up, authorities staff could record local series notes, which would eliminate the need for the shared local series authority. LCA10 is updated, but the local file is not. Having to check both files is problematic.
  • SBTF Members will take back to Deans to go through MCLS: Seek funding for and support automated authority maintenance solutions. (The possibility of centralized authority control was historically a primary impetus for merging the SUL databases.)

Priorities relating to the Florida Academic Repository (FLARE)

  • Establish FLARE as an ADM library within the Shared Bib client; configure permissions / processes /workflows to facilitate transfer of material to FLARE.
  • Reconfigure process for updating OCLC serial holdings post-shared bib, and to accommodate the implementation of FLARE.


Possible projects that FLVC may be able to do

  • Take greater responsibility for coordinating batch data loads; whenever possible FLVC staff should do the batch loads themselves. (The SB Data Loading group agreed that batch data loads should be coordinated; it now appears that more central coordination by FLVC is needed.)
  • Run ACRL statistics for SULs because many libraries need these same numbers.
Personal tools