All work
- Retire mod-kb-ebsco (Ruby) projectMODKBEBSCO-23Resolved issue: MODKBEBSCO-23
- Q4 2018 releaseMODKBEBSCO-22Resolved issue: MODKBEBSCO-22Carole Godfrey
- Security vulnerability reported in rack >= 2.0.4, < 2.0.6MODKBEBSCO-21Resolved issue: MODKBEBSCO-21Sobha Duvvuri
- Security vulnerability reported in loofah @ 2.2.2MODKBEBSCO-20Resolved issue: MODKBEBSCO-20Sobha Duvvuri
- Create RAML documentation for status endpointMODKBEBSCO-18Resolved issue: MODKBEBSCO-18Sobha Duvvuri
- Create RAML documentation for configurationMODKBEBSCO-17Resolved issue: MODKBEBSCO-17Sobha Duvvuri
- Update Titles Search to support searchType param/Remove advancedSearch paramMODKBEBSCO-15Resolved issue: MODKBEBSCO-15Carole Godfrey
- BUG: Proxy 'id' must be present error when select/deselect packagesMODKBEBSCO-16Resolved issue: MODKBEBSCO-16Carole Godfrey
- Release v1.0.0 for FOLIO 2018q3MODKBEBSCO-4Resolved issue: MODKBEBSCO-4Sobha Duvvuri
- BUG: mod-kb-ebsco - 'invalid url error' when editing a title with empty urlMODKBEBSCO-5Resolved issue: MODKBEBSCO-5Carole Godfrey
- Create RAML documentation for root-proxiesMODKBEBSCO-9Resolved issue: MODKBEBSCO-9Sobha Duvvuri
- Create JSON schemas for getting list of packages associated with a providerMODKBEBSCO-13Resolved issue: MODKBEBSCO-13
- Refactor titles endpoint and remove `q` as a optional in mod-kb-ebscoMODKBEBSCO-8Resolved issue: MODKBEBSCO-8Sobha Duvvuri
- Update RAML docs: Remove q from the title endpoint docsMODKBEBSCO-10Resolved issue: MODKBEBSCO-10Sobha Duvvuri
- Update RAML documentation to include tokensMODKBEBSCO-7Resolved issue: MODKBEBSCO-7Carole Godfrey
- Create RAML documentation for custom-labelsMODKBEBSCO-12Resolved issue: MODKBEBSCO-12
- mod-kb-ebsco and mod-codex-ekb should store rm api credentials in same location (backend)MODKBEBSCO-6Resolved issue: MODKBEBSCO-6Carole Godfrey
- Spike: Export eHoldings: Investigate RM API responsesMODKBEBSCO-11Resolved issue: MODKBEBSCO-11
Retire mod-kb-ebsco (Ruby) project
Description
Environment
Potential Workaround
relates to
Checklist
hideTestRail: Results
Activity
David CrossleyJanuary 6, 2020 at 6:27 AM
Done. The old repository is now "archived read-only" as explained in my comments above and at FOLIO-2251.
Peter MurrayDecember 20, 2019 at 4:02 PM
A new security advisory popped up for the old `mod-kb-ebsco` code.
David CrossleySeptember 11, 2019 at 1:09 AM
I added the new ticket FOLIO-2251 for the Core Platform Team to rename and archive, as explained in my previous comment above.
However, this current Sprint 72 is very busy, so it may need to wait.
Carole GodfreySeptember 10, 2019 at 1:22 PMEdited
Sure I think that makes sense and
Would this be a good reference https://medium.com/maintainer-io/how-to-deprecate-a-repository-on-github-8f0ceb9155e for steps we should take to do this?
Also found this reference on archiving the repository
https://github.blog/2017-11-08-archiving-repositories/
Peter MurraySeptember 10, 2019 at 1:09 PMEdited
: Is it okay if we mark this Ruby-based project as Deprecated in GitHub? It'll stop the security alerts in addition to signalling to others that the code is no longer used
and , what do you guys think?
Now that mod-kb-ebsco-java project has been released with Q1 and replaces functionality that was in mod-kb-ebsco (ruby module) – we should retire the older mod-kb-ebsco ruby version project.
#devops or #releases channels may have instructions on what steps are needed
Should mod-kb-ebsco-java project be renamed to mod-kb-ebsco?