Acquistions in the Shared Bib Environment

From SharedBib

Jump to: navigation, search



  • Project status
    • Not ready for testing
      • Data Loading
      • Scheduled notices, reports and other jobs that run on a regular schedule (joblists)

Big Picture Differences

  • Aleph Architecture changes
  • Conceptual change about bib record ownership
    • No ownership of bibs. SUL association with a Bib is via HOL or Items
  • Important distinction between sharing/not sharing
    • Bib records shared, HOL file shared, see all HOLs, can edit only yours
    • Permissions shared
    • ADM records not shared: budgets, vendors, invoices, orders, circulation
  • Goal is to not have duplicate Bib records
  • Shared configuration tables in Bib. and HOL files may mean joint decision making on settings
  • Combined bib records
    • Bigger records, some tags marked as shared, some local ($5), All SULs can edit all bib. records
  • Different Aleph numbers: transition process includes renumbering some, relinking everything
  • At each library

Acquisitions and Serials

  • Visible changes in the Aleph client
    • Some drop down of options may contain all SUL lists (in shared libraries, BIB and HOL) Example
    • Searching:
      • Default is full set of Bib records (UXU01); option to search local base
        • Example: #017633678 Adagio, WoO 35
      • Default is full set of HOL records, need to limit by sublibrary
        • Example: #12333130
    • Navigation: Functional and Overview:
      • Bib, HOLs, Items, Orders -Example: #14879172
      • Moving Order Records form one bib to another -Example: #12060440 to #13530231
    • Orders:
      • No item record or HOL record #1630556-1
      • Item record not linked to Order, no HOL #15589395-1
      • Item linked order, no HOL #11385267-1
      • Item not linked to Order, HOL #1630477-1
      • Item linked to order, HOL #1559045-1
      • Dummy Payment Records #1507249-4
  • Data Loading
    • Consider the combined workflow of the SULs
    • Some centralized loading by FCLA/FVC
    • Coordination of future loads
  • Separate ADM XXX50 Libraries:
    • Searching Order Index, Invoices, Budgets, Vendors
    • EDI invoice loads
    • Serials Check-in
    • All Budget activities
    • Separate Vendor files
    • Separate Scheduling of End of Fiscal Year Rollover Services
  • Mango
    • Little impact on users; look the same; Local catalogs continue as is
    • Acquisitions Order Status Display from Item Record IPS
    • Bib/HOL/Items/Order Matrix
    • Bib. ownership changes impact what shows in Mango in local catalog
  • Reports:
    • Aleph or Arrow reports that include Bib info. will change, others might

Transition tasks

  • FCLA is responsible for all FCLA provided services such as:
    • No change for accounts payable (APFeed)
    • Custom services like loading object codes after EDI invoicing
  • Libraries are responsible for local initiatives such as:
    • Macros (MacroExpress)
    • Locally created reports based on Oracle access
    • Other locally created scripts in Aleph
Personal tools