Versions Compared

Old Version 3

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 4

changes.mady.by.user Andrea Bollini (4Science)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Discuss Strategies for replacement.
    1. (Option 1) Quick Replacement
      1. Remove all BTE code immediately, replacing with Live Import implementations.
      2. 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)
      3. May be less development work overall, as it doesn't involve having to write a BTE plugin for Live Import (see next option)
    2. (Option 2) Transition by temporarily wrapping BTE
      1. Create a BTE plugin for Live Import.
      2. 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)
      3. 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.
      4. Remove BTE entirely once "major" formats have been migrated to Live Import. (Need to determine which formats are considered "major".)
    3. (Option 3)
      1. create a live import implementation of the extract panel
      2. add support for file in live import to provide support for RIS,EndNote,BibTeX
      3. avoid any further development on top of BTE and incentivate porting of BTE feature to the live import framework
    4. (Other options?)
  2. Discuss timelines for replacement
    1. (Option 1) BTE is completely removed by 7.0 Final.  Ensure all/most formats previously supported by BTE are either supported by Live Import, or scheduled for 7.1 or 7.2 (if needed).
    2. (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)
    3. (Other options?)

...