Contribute to the DSpace Development Fund
The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.
Date
from 14:00-15:00 UTC
Location: https://lyrasis.zoom.us/my/dspace (Meeting ID: 502 527 3040).
- More connection options available at DSpace Meeting Room
References
- As noted in 2020-05-07 DSpace 7 Working Group Meeting, BTE will be replaced by Live Import per the ticket at
- Currently, the two frameworks support differing sets of formats:
- Live Import in v7 currently supports LoC Names, Sherpa RoMEO, ORCID and PubMed (via "External Sources", see https://github.com/DSpace/DSpace/blob/master/dspace/config/spring/api/external-services.xml and https://github.com/DSpace/Rest7Contract/blob/master/external-authority-sources.md)
- BTE in v6/7 current supports ArXiv, CiNii, CrossRef, PubMed (in DSpace codebase) and OAI-PMH, BibTeX, CSV, Endnote, Excel, and RIS (in BTE codebase)
- Bolded items are not yet supported by Live Import
Agenda
- Discuss Strategies for replacement.
- (Option 1) Quick Replacement
- Remove BTE entirely
- Build up Live Import
- Remove all BTE code immediately, replacing with Live Import implementations.
- Will cause loss of functionality for JSPUI users. As noted above, there are formats BTE supports that Live Import doesn't yet support (until each can be implemented)
- May be less development work overall, as it doesn't involve having to write a BTE plugin for Live Import (see next option)
- (Option 2) Transition by temporarily wrapping BTE
- Create a BTE plugin for Live Import.
- Remove BTE from usage(s) in REST API v7, replacing with Live Import. Live Import can temporarily use BTE to process files/services that it doesn't yet support (no immediate loss of functionality)
- Transition BTE "data loaders" / services into Live Import "data providers". Perhaps migrate one format as an initial example. That would provide a reference example to other developers to migrate other formats.
- Remove BTE entirely once "major" formats have been migrated to Live Import. (Need to determine which formats are considered "major".)
- (Option 3)
- Deprecate BTE (no further BTE development allowed)
- Build up Live Import to match BTE base features (An example file importer, and an example of migrating one importer from BTE to Live Import)
- First two would be funded. Others may need to be volunteer-based, depends on funding available.
- (Based on what we learn in migrating first two plugins, we'll decide whether to create a BTE plugin for Live Import: 1-2 days of work)
- Remove BTE entirely
- (Other options?)
- (Option 1) Quick Replacement
- Discuss timelines for replacement
- (Option 1) BTE is completely removed by 7.0 Final (ideally, but will need to be finalized based on what we learn migrating the first two plugins). Ensure all/most formats previously supported by BTE are either supported by Live Import, or scheduled for 7.1 or 7.2 (if needed).
- (Option 2) BTE is completely removed by 7.1 or 7.2. Would require disabling BTE by default and placing warnings about possible security issues (especially DOS/Out-of-memory attack which seems possible in the Excel data loader)
- (Other options?)
Attendees
Notes
Overview
Content Tools