Project Summary Section

Summary

This swimlane is to develop a minimally viable product for the implementation of controlled digital lending (CDL) functionality as part of ReShare Returnables. Key CDL functionality includes:

• Display of CDL delivery options;

• Addition of CDL workflow features to the lending library side; and

• Addition of digital delivery option.

Rationale and Strategic Fit

This work potentially benefits any consortium using Returnables. It will add an option for libraries to digitally share materials that they hold in their physical collection. It will also facilitate collaborative CDL in a consortial setting.

Ultimately, this swimlane adds the capability to support consortial CDL and adds further functionality which brings ReShare closer to supporting nonreturnables.

Goals

What measurable or demonstrable outcomes should be achieved by the end of this project?

• Phase 1 (MVP)

  • Requests can be forwarded from an institution’s resource sharing system (e.g. ILLiad) to ReShare

    • [more detail about what the patron sees over time in the home resource sharing account]

  • Requests can be placed for CDL items in the ReShare VuFind interface

  • Patron can see all of their historical requests (CDL and otherwise) in the VuFind account pages

  • Consortial holdings index reflects whether an item can be lent via CDL using a specified set of rules, e.g. publication date, location, etc.

  • A default CDL loan policy (i.e. duration) can be set at the consortial level and overrode at the request level when fulfilling a loan request

  • ReShare checks source ILS to determine availability of a title and copy

  • ReShare communicates with source ILS to make a lent item unavailable when the request is fulfilled, and available when it is completed

  • Print pull slips for CDL items

  • ReShare uses a rota to identify the supplying library

  • Request states to support ReShare:

    • Awaiting staff review

    • Awaiting shelf availability check

    • Awaiting digitization

    • Loaned via CDL

    • Awaiting return to shelf

    • Request completed

    • Request canceled

  • Patron gets an email with the info about their CDL loan

  • Basic analytics are available to libraries and at the consortial level

• Phase 2 (not yet resourced)

  • Integration with an external repository of digitized files.

• Phase 3 and beyond (not yet resourced): assumption is that this list of functionalities will change/grow as libraries adopt CDL during phase 1 and 2

  • Patron can renew their CDL loans

  • Patron can “return” their CDL loan early

  • Libraries can opt in/out of CDL sharing

  • A library can mark specific locations as dark storage and already digitized, which will bypass the awaiting shelf availability check and return to  shelf stages of the workflow

  • Patron requests can be queued in a waitlist

  • Offer an escape route for unfilled requests

Stakeholders

• What institutions are providing funding for this project?

  • Boston Library Consortium

  • Midwest Collaborative for Library Services

  • Duke University (potentially)

• What ReShare groups have a stake in the outcome of this project?

  • Any consortium using or considering the use of Returnables with an interest in CDL.

• What non-ReShare groups need to be kept updated on the status of this project?

Questions

What questions do the EC, SC, and PM team have about this swimlane?

Project Charter Section

Project Team

Requirements

Scope

• What is in scope for this swimlane?

• What is out of scope for this swimlane?

Estimated Schedule

• Deadline

• Sprint cycles

Completion Criteria

• This swimlane will be considered complete when…

Dependencies

• What other projects/tasks depend on this swimlane being completed?

• What other projects/tasks must be completed before this swimlane can begin?

Implementations & Other ReShare Priorities

• This swimlane is resourced with new funding specifically associated with this work. It does not take development or planning resources away from the core of the project.

• SMEs should be recruited from interested organizations -- should not take SME resources away from core work

• What simultaneous work do we deem to be acceptable?

  • Core maintenance

  • MOBIUS RFP development

  • ReShare implementations by new libraries/consortia handled via the change management process defined below.

Collaboration and Communication Strategy

• Monthly reports by the product owner and product manager to ReShare Executive Committee and Steering Committee

• To which non-ReShare groups?

Risks

Timeline

Change Management

• What is the process for changing timelines and resourcing?

Budget

Ownership of Intellectual Property

Describe who will own any intellectual property created as a result of the Contract. This may include aspects relating to work-for-hire, confidentiality, open source, derivative works, etc.

Payment Schedule and Sources of Funding

• What amounts will be paid by ReShare?  To whom?  When?

• What amounts will be paid to ReShare?  By whom?  When?

Technical Requirements Section

Hardware and Software Technology Requirements

• What server or cloud resource requirements are needed for this swimlane?

  • TBD

• What operating system?

  • Linux

• What development languages will be used?

  • Groovy/Grails (native environment of Returnables backend); React/FOLIO Stripes (frontend)

• What will be included in the software stack?

  • Augmentations to ReShare Returnables (frontend and backend)

Testing & QA

• What continuous testing procedures will be followed during this project?

  • Automated unit and integration testing

• What community testing procedures will be followed during this project?

  • Testers will be recruited from project stakeholders and interested libraries

Deployment

• What are the anticipated deployment procedures?

  • Deployment will be part of ReShare returnables

  • Additional policies and configurations specific to CDL will apply

  • A separate repository and access portal or DRM system will need to be provisioned

• What impact will deployment have on other ReShare functions?

  • None

• What impact will deployment have on existing ReShare users?

  • None

Documentation

• Who will develop technical documentation?

  • Development team

• Who will develop user (library staff) documentation?

  • Product owner and stakeholder-contributed staff

• Where will these live?

  • In the ReShare Returnables documentation system

Project Maintenance Plan

ReShare Core Implications

• What components of this project will ultimately be added to the core?

  • This project is almost entirely focused on additions to the core.

  • Possible minor contributions to VuFind may be made to facilitate patron status inquiries.

• What are the projected resources required to maintain this as part of the core?

  • 10-20% of development costs per year: 2.4-5 person-weeks per year (“rule of thumb” estimate)

• What is the source of funding for ongoing maintenance?

  • TBD

ReShare Adjacent Implications

• What components of this project will be maintained by a Certified Service Provider?

Ongoing Support

• What types of issues will be resolved by the CSP only?

  • Deployment and configuration;

  • Tier-1/tier-2 support

• What types of issues will be considered as the responsibility of the ReShare community?

  • Foundational software support and maintenance

Future Development

• What planning process will be used to move the swimlane beyond MVP?

  • The swimlane operates its own product management team

  • Initial steps beyond MVP have been identified (see above)

• Who should be involved in this planning process?

  • Swimlane product management team

  • Liaise with SC and core product management team

• What is the estimated timeline for beginning this planning process?

  • During development of MVP