resource_sharing
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
resource_sharing [2022/01/16 11:19] 81.155.150.187 |
resource_sharing [2022/01/16 11:24] 81.155.150.187 |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| ===== Rapid ILL ===== | ===== Rapid ILL ===== | ||
| - | RapidILL was developed by inter-library loan staff at Colorado State University and subsequently acquired by Ex Libris. It facilitates quick, reciprocal resource requesting for ‘pods’ of libraries and interfaces with software solutions from a variety of vendors. It is optimised for ‘non-returnables’ (i.e. electronic copies such as journal articles, rather than print resources such as books) and offers the following features:\\ | + | [[https://exlibrisgroup.com/products/rapidill-interlibrary-loan/|RapidILL]] was developed by inter-library loan staff at Colorado State University and subsequently acquired by Ex Libris. It facilitates quick, reciprocal resource requesting for ‘pods’ of libraries and interfaces with software solutions from a variety of vendors. It is optimised for ‘non-returnables’ (i.e. electronic copies such as journal articles, rather than print resources such as books) and offers the following features:\\ |
| RapidILL ‘pods’ are groups of libraries (a pod could be all NHS libraries in England) that have agreed to freely share journal article and e-chapters and commit to supplying these within 24 hours. Their holdings are loaded into RapidILL via automatic, monthly OAI-PMH harvesting. | RapidILL ‘pods’ are groups of libraries (a pod could be all NHS libraries in England) that have agreed to freely share journal article and e-chapters and commit to supplying these within 24 hours. Their holdings are loaded into RapidILL via automatic, monthly OAI-PMH harvesting. | ||
| RapidILL provides load balancing to ensure that each library receives as many copies as they supply. When sourcing items, it selects the holding library with the lowest net number of requests. | RapidILL provides load balancing to ensure that each library receives as many copies as they supply. When sourcing items, it selects the holding library with the lowest net number of requests. | ||
| - | Once requests are fulfilled, details are transferred to and held within the local LMS/ILDS systems with which RapidILL interfaces. This means that user data is held only temporarily in RapidILL, and requests managed and user data held on local systems. With the Alma LMS and CLIO ILDS system, there is full integration and the transfer of requests is automatic. This level of integration does not yet exist for other systems and manual data transfer is required. | + | Once requests are fulfilled, details are transferred to and held within the local LMS/ILDS systems with which RapidILL interfaces. This means that user data is held only temporarily in RapidILL, and requests managed and user data held on local systems. With the Alma LMS and CLIO ILDS system, there is full integration and the transfer of requests is automatic. This level of integration does not yet (July 2021) exist for other systems and manual data transfer is required. |
| ===== Tipasa ===== | ===== Tipasa ===== | ||
| \\ | \\ | ||
| - | Tipasa is supplied by OCLC and described as ‘an ILL management system for individual libraries to share and obtain materials through different resources and systems as well as to provide an exceptional experience for the library user’. Unlike RapidILL, it is designed to manage both ‘returnables’ and ‘non-returnables’. | + | [[https://www.oclc.org/en/tipasa.html|Tipasa]] is supplied by OCLC and described as ‘an ILL management system for individual libraries to share and obtain materials through different resources and systems as well as to provide an exceptional experience for the library user’. Unlike RapidILL, it is designed to manage both ‘returnables’ and ‘non-returnables’. |
| - | Tipasa claims to be system agnostic but currently only integrates with OCLC WMS, Ex Libris Alma and CLIO. It uses a ‘proven sender’ concept, with libraries designated as proven senders where they have demonstrated that they provide good quality documents quickly. Optionally, Tipasa offers Article Exchange, a secure area for article delivery where staff can place requests for users to download . | + | Tipasa claims to be system agnostic but currently ( (July 2021) only integrates with OCLC WMS, Ex Libris Alma and CLIO. It uses a ‘proven sender’ concept, with libraries designated as proven senders where they have demonstrated that they provide good quality documents quickly. Optionally, Tipasa offers Article Exchange, a secure area for article delivery where staff can place requests for users to download . |
| Tipasa uses the NCIP protocol to integrate with local LMS circulation systems to create temporary records in circulation systems. Unlike RapidILL, Tipasa can also manage requests made to fee-based services such as Reprints Desk. Conversely, libraries which charge for document supply can be excluded. | Tipasa uses the NCIP protocol to integrate with local LMS circulation systems to create temporary records in circulation systems. Unlike RapidILL, Tipasa can also manage requests made to fee-based services such as Reprints Desk. Conversely, libraries which charge for document supply can be excluded. | ||
| Line 36: | Line 36: | ||
| \\ | \\ | ||
| - | Project ReShare is an open-source community driven project ‘creating a new and open approach to library resource sharing systems that sets the standard for how we connect library patrons to the resources and information they require…..designing an open source, highly-scalable platform that supports discovery, fulfilment, and delivery workflows, with a focus on user-centered design’. | + | [[https://projectreshare.org/|Project ReShare]] is an open-source community driven project ‘creating a new and open approach to library resource sharing systems that sets the standard for how we connect library patrons to the resources and information they require…..designing an open source, highly-scalable platform that supports discovery, fulfilment, and delivery workflows, with a focus on user-centered design’. |
| - | Although not formally part of the Folio open source LMS initiative, Project ReShare uses the same core developers IndexData and the Folio technical infrastructure and has much of the same community ethos. Although community-owned and driven, it encourages libraries and commercial organisations to participate meaningfully in advancing its goals. Currently the community of libraries actively engaged with project ReShare is exclusively US-based. ReShare supports consortial, peer-to-peer borrowing between defined resource sharing groups, which can restrict resource sharing amongst themselves. It has a strong focus on interoperability, using standards such as NCIP, Z39.50, ISO10160 and ISO18626. Its current focus is returnables. Non-returnables are on the road map but with no clear date. | + | Although not formally part of the Folio open source LMS initiative, Project ReShare uses the same core developers IndexData and the Folio technical infrastructure and has much of the same community ethos. Although community-owned and driven, it encourages libraries and commercial organisations to participate meaningfully in advancing its goals. Currently the community of libraries actively engaged with project ReShare is exclusively US-based. ReShare supports consortial, peer-to-peer borrowing between defined resource sharing groups, which can restrict resource sharing amongst themselves. It has a strong focus on interoperability, using standards such as NCIP, Z39.50, ISO10160 and ISO18626. Its current focus is returnables. Non-returnables are on the road map (July 2021) but with no clear date. |
resource_sharing.txt · Last modified: 2024/03/06 04:56 by paul
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC0 1.0 Universal
