Codex (UXPROD-833)

[UXPROD-871] Updates to mod-codex-ekb Created: 10/Jun/18  Updated: 16/Sep/20  Resolved: 16/Oct/18

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2018
Parent: Codex

Type: New Feature Priority: P3
Reporter: Khalilah Gambrell Assignee: Khalilah Gambrell
Resolution: Done Votes: 0
Labels: resourcemanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to MODCXEKB-64 Update mod-codex-ekb to support Boole... Closed
relates to MODCXEKB-68 Return Subjects in mod-codex-ekb resp... Closed
relates to MODCXEKB-69 Support search by subject Closed
relates to UIEH-429 Add parameter advancedsearch=true to ... Closed
Epic Link: Codex
Analysis Estimate: Small < 3 days
Analysis Estimator: Khalilah Gambrell
Front End Estimate: Medium < 5 days
Front-End Confidence factor: Medium
Back End Estimate: Medium < 5 days
Estimation Notes and Assumptions: - Medium for mod-codex-ekb backend work (CG)
- Need to consider work for the multiplexer?
Development Team: Spitfire
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R4
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R1

 Description   

Pending updates to EBSCO KB API in late June/early July timeframe. mod-codex-ekb updates will be needed to support

  • Display Contributor on Results List
  • Ability to conduct Boolean/Exact Phrase/Keyword Searching


 Comments   
Comment by Carole Godfrey [ 25/Jun/18 ]

Estimate for dev effort is "Medium < 5 days" - 1 developer

  • Minor effort to include contributor on result list - already available in single record lookup - supported in RAML/Instance model
  • As part of implementation would like to be provided with sample CQL queries to better understand intended usage for the boolean and exact phrase searching (so to properly translate to RM API advanced search query)
  • need to confirm ascending/descending functionality availability in RM API
Comment by Theodor Tolstoy (One-Group.se) [ 09/Oct/18 ]

This is marked as being "in progress", but it is not tied to any release. Will this get done in time for the q4 release?

Comment by Khalilah Gambrell [ 09/Oct/18 ]

Theodor Tolstoy (One-Group.se) - yes this will get done in Q4 2018. I updated this feature with the release date.

Comment by Theodor Tolstoy (One-Group.se) [ 10/Oct/18 ]

Thank you Khalilah Gambrell

Comment by Cate Boerema (Inactive) [ 11/Oct/18 ]

Khalilah Gambrell, who is the development team on this? The issues says "Core team", but this didn't make the Q4 cut for the Core team (which is why I removed the Q4 fix version). Of course, if another team is taking care of it, that's awesome! Can you please let me know and update the development team accordingly? Thanks much!

Comment by Khalilah Gambrell [ 11/Oct/18 ]

Cate Boerema - Carole/Sobha of the Spitfire team is working on this feature.

Comment by Cate Boerema (Inactive) [ 11/Oct/18 ]

Brilliant! Thanks

Generated at Fri Feb 09 00:11:03 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.