Archive for the ‘FulfILLment’ Category

FulfILLment Webinar Now Available

Thursday, September 11th, 2014

Equinox Vice President Grace Dunbar recently hosted an online webinar in partnership with LYRASIS.  This webinar is a great introduction to FulfILLment.  If you were unable to attend the class in real time, you may view the recording here.  This recording is also available under Documentation and Resources on the FulfILLment site.

Click to view Powerpoint

Announcing FulfILLment Testing Pilot Project

Wednesday, September 26th, 2012

The Pacific Library Partnership, consisting of three libraries in California, has contracted with Equinox Software, Inc. to test FulfILLment.  The partnership consists of Los Gatos Public Library, Peninsula Library System (the city of San Mateo only), and Santa Cruz Public Library.  These libraries currently use Koha, Millennium, and Evergreen as their ILS.  Lori Bowen Ayre, The Galecia Group, is serving as a consultant on this project as part of the Open Source – Open Libraries project.  The partners will be testing FulfILLment to see if it can meet their requirements for managing physical item resource sharing between independent library systems.  FulfILLment was developed by Equinox developers with funding from OHIONET and other development partners including:  the State Libraries of Ohio, Indiana, Illinois, South Carolina, Iowa, Kansas, Missouri, and WiLS.  It is anticipated that FulfILLment version 1.0-RC1 will be available in the spring/summer of 2013.

FulfILLment is generally described as an open source ILL software, but it is so much more.  It is an open source, regional resource-sharing system between disparate ILS.  It was designed to bridge otherwise incompatible software products so that different libraries can continue to use their current ILS while obtaining many benefits enjoyed by libraries using Evergreen in resource-sharing consortia.  The development of LAIs (Local Automation Integrator) in FulfILLment makes this possible by allowing the participating libraries to obtain bibliographic and other relevant information from each library’s current automation system and making this information accessible over the internet.  FulfILLment is also scalable.  If necessary, new custom LAIs can be developed in future versions of FulfILLment to allow even more libraries to join and enjoy all that FulfILLment has to offer.

Get to know your friendly, neighborhood open source ILL better! This week in FulfILLment: Patron and Staff Use

Wednesday, February 8th, 2012

Below is a brief overview of how patrons will be able to use FulfILLment:

  • Patrons will access the NGDI (next generation discovery interface) through the find elsewhere (customizable) link in their home catalog.Clicking the link will allow them to browse the union catalog of libraries connected through FulfILLment.After choosing the material they want, the patron has to authenticate (if not already logged in) and complete the request.
  • Patrons will be able to specify a need by date.
  • Patrons will be able to opt-in for email notification when a request need by date is expiring and use the link to the request to change the date or cancel.
  • Notifications of cancelations and items ready for pick-up can be made via email or print.Although FulfILLment will not be able to do print notices itself, it will be configurable to output PDFs or it can be integrated with a third party printer like Unique.
  • Patrons will be able to select pick-up location.
  • Patrons will be able to suspend requests that are unfilled and reactivate them at a later time.
  • If a patron requests a serial, the interface will ask for volume and number information.Patrons may also include more specificity (example: article on page 30 by Smith) in the notes field.

Below is a brief overview of how Staff will be able to use FulfILLment:

  • Staff will be able to access a pull list from the FulfILLment interface which will display and print a list of items that have been requested.This list can be run at any time.
  • Staff will pull requested items from the shelf and scan the item barcodes in another FulfIllment interface screen.The system will print a receipt or wrapper upon barcode scan.
  • With proper permissions, staff may use the interface to also edit, delay, or reject a request.
  • If the request is rejected, the system will automatically try to find another copy to fill the request.
  • Staff may search by request ID or any other field title, patron name, barcode, etc.
  • Staff has the option of targeting a specific copy at a specific library when placing a request for a patron.Patrons will not have this option.

Permit me to tell you about…Policies and Permissions in FulfILLment!

Friday, January 27th, 2012

Policies and Permissions in FulfILLment will be very flexible and highly configurable. Read on to learn more.

    • FulfILLment will have the ability to create policies to determine/control patron eligibility. This is flexible down to specific libraries or specific item types.
    • Authorized staff will be able to create org groupings to funnel patrons into searching pre-defined groups (county-wide, regional, state, school, etc.).
    • FulfILLment will allow blocking of material types at specific libraries from filling ILL for all or specific patrons or groups.
    • Circulation policy can be generated from either the owning or lending library policies.
    • When an item is put in transit to a library to fill an ILL request, a brief bib record is pushed to the home ILS system (if the system permits it) to facilitate checkout. If the home ILS does not permit it, then staff will need to create a brief record.
    • The Administration module will allow local definition of what actions staff may perform and at what locations.
    • The Administration module also allows fine granularity of policies and permissions to be set/configured. Here are a few examples:
      1. The ability to configure max requests per patron.
      2. The “Need by date for material can be configured.
      3. Org units can be configured to be valid pick-up locations.
      4. The ability to designate a library to be the lender of last resort.
      5. Renewals will be configurable on a material type or library-by-library basis.
      6. The ability to configure standard processing charges per library. This amount will be visible to patrons in My Requests.

Remember to check back next week. Next week’s post will cover Patrons and Staff Use in FulfILLment.

We’re in the homestretch!

Monday, November 7th, 2011

We are in the final phase of development on the FulfILLment project. Equinox developers Mike Rylander and Michael Smith have been hard at work making improvements, adding functionality to the interface, and making progress on the connectors. The interface now includes transit tracking and enhanced filtering.  The transit tracking UIs allow staff to see ILL transits that are currently in transit. There are many more options for filtering, including allowing filtering by library. Users will appreciate being able to sort the results in a variety of ways. The interfaces are also faster now since some changes were made to the way data is refreshed. Another exciting update is the selection of the final list of connectors to be built as part of the initial development phase of this project. They are (in no particular order):
1. Innovative Interfaces Millenium ILS
2. SirsiDynix Symphony
3. Polaris
4. Ex Libris Aleph
5. Koha
Stay tuned for 2012! It’s going to be an exciting year.

FulfILLment Development Update

Thursday, May 12th, 2011

We are now in the sixth quarter of FulfILLment development at this point in the project. The finish line is nearly in sight. ESI developers, Michael Smith and Mike Rylander have been busy at work streamlining corner cases to make the import of items smoother. The jangle core has been completely integrated into the main body of the FulfILLment code, providing speed advantage. The record ingest is more streamlined now. System tests with the iii connector and the Z39.50 interface have been successful. This will make building future connectors easier. The LAI layer can now pull records in from the iii connector and can show interlibrary loans to and from a library. By the end of this quarter, we hope to have a number of the FulfILLment specific interfaces done. Also, we will have completed more work on the UI and will have more to show in this area. Stay tuned.

Update on First and Second Quarter FulfILLment Development

Monday, August 2nd, 2010

On July 22, 2010, Mike Rylander, VP of Research and Design for Equinox Software, Inc. (ESI) presented a webinar on the development that has occurred during the second quarter of the FulfILLment project. This is a two year project with an anticipated completion date of December 2011. Mike Rylander is the Lead Developer on the project, with the assistance of Michael Smith, ESI Developer, and Suzannah Lipscomb, ESI Project Manager.

During the second quarter, Mike and Michael continued to build upon the foundation established in the first quarter. Development occurs, sometimes simultaneously, at three different levels: database (or bottom), business logic (or middle) and user interface (UI). Much like building a house, necessary infrastructure must be created and put in place so that desired functionality can later be built on top or extended.

Database and user interface development occurred during the first quarter. The database development involved the following: record ownership; Next Generation Discovery Interface (NGDI); and automated record ingest. Regarding record ownership, fields were added to record record ownership. This will allow filtering of record visibility based on the institutions that own a title, regardless of item availability which is unknown or not authoritative at the time of searching. Later in the process, there will also be visibility checking of individual copies. Also, infrastructure was built which allows for permissions required to edit bib records directly in FulfILLment and for using record ownership instead of copy visibility for search result filtering. The NGDI completed work involves the generalized query infrastructure and true faceting support. For the generalized query infrastructure, the replacement query infrastructure, required for most search-related features, was built. For true faceting support, the functionality to cache and deliver query-specific faceting data was built. Regarding automated record ingest, rule sets were developed which will be applied to incoming records to facilitate normalization and data insertion. Additionally, an in-database ingest of incoming and updated records will speed up and increase the flexibility of record caching, while automated pipelining will facilitate the ingest of full and differential record additions without human intervention. UI development also occurred in the first quarter. The ILL requests (holds) list was developed which will allow patrons to view the status of, and change parameters of, ILL requests (holds) placed through the FulfILLment NGDI. Also, in order to support the interface for placing holds directly on metarecords, the interface extensions, providing the ability to place holds directly on metarecords from the main result screen, were built.

Development on the database in the second quarter continued to build on the work in the first quarter. For example, the developers worked on breaking up search logic in preparation for record-level visibility testing, which is dependent on the NGDI work completed in the first quarter. Additionally, development has been completed which will allow the ability to cache item visibility information for non-authoritative record visibility display. This work will result in faster searching capability because of the distinction between record ownership and copy location. Caching based on record ownership, as opposed to items simply involved in ILL transactions, makes the caching process more efficient and makes the display process faster. General testing of the Ruby Jangle Core implementation began with Evergreen (EG) being targeted as the downstream source. Initial testing results indicated the jangle core has robust capability. Some progress on user caching was completed with the EG prototype connector implementation of Jangle Actor Application Programming Interfaces (APIs). Approximately 30 – 40 percent of the actor API work in connection with the EG Connector has been completed and work on the EG Connector has already begun. In preparation for the work which will occur on LAI Connectors, dataflow diagram and design work for connectors was completed. More work was completed on NGDI, specifically infrastructure and UI widgets for skinning of search/discovery interfaces. The automated record ingest development from first quarter was streamlined by extending rule sets and application while providing and extending APIs for foreign record ingest. The API work allowed Mike, at the request of OhioNet, to upload approximately 90,000 metarecords and optimize them so that a variety of metarecords may be examined in detail. More work was completed on cache purging to allow automatic purging of item and patron data on a scheduled basis to automatically expire stale, cached data. In terms of UI work, the EG results screen is stabilized now. This is the result of the work on the ingest pipeline and how records are pulled in. Bibtemplate functionality was added which provides a richer display and allows Google Book Browse to be turned on. Finally, developer documentation is in progress with more technical detail regarding the specifics of this development.

Fulfillment Blog

Wednesday, March 10th, 2010

Welcome to the Fulfillment Blog.  Check here often to stay up to date with information about the Fulfillment project.