eHoldings App
(UXPROD-830)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q1 2020 | Parent: | eHoldings App |
| 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: |
|
||||||||||||
| Epic Link: | eHoldings App | ||||||||||||
| Analysis Estimate: | Small < 3 days | ||||||||||||
| Analysis Estimator: | Khalilah Gambrell | ||||||||||||
| Front End Estimate: | Large < 10 days | ||||||||||||
| Back End Estimate: | Large < 10 days | ||||||||||||
| Development Team: | Spitfire | ||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R2 | ||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R1 | ||||||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||
| Rank: hbz (TBD): | R4 | ||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||||||
| Rank: TAMU (MVP Jan 2021): | R3 | ||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||
| Description |
|
Support EBSCO functionality of adding customer specific information at the Title level |
| Comments |
| Comment by Anya [ 16/Oct/19 ] |
|
FC: Can we revisit this "wont do" – can we ask Why ? |
| Comment by Khalilah Gambrell [ 16/Oct/19 ] |
|
Anya, we decided not to do it because of the use of tags. Does FC currently use Custom labels in HLM? |
| Comment by Anya [ 16/Oct/19 ] |
|
Khalilah Gambrell-- jmulvaney@library.umass.edu I believe so – but Jack would be able to answer this question more thoroughly. |
| Comment by jmulvaney@library.umass.edu [ 17/Oct/19 ] |
|
I think tags don't quite match the functionality available in HLM. Custom Labels can be staff or user facing. We are not yet using Full Text Finder so they aren't configured but as of right now we would at least need them for internal notes fields that shouldn't be used as tags. In our current link resolver we have notes denoting what package something might be a part of, PA access with years, Order #'s for comes-withs, and random notes on access issues. These custom fields can be exported via HLM the same way internal notes can be exported via SFX and we don't want to lose this functionality. I also hope to use them for previous/continues by notes for name changes since the EKB does not have robust previous title linking. I can ask two of my colleagues using FTF if they have started using these fields. |
| Comment by Khalilah Gambrell [ 17/Oct/19 ] |
|
Thanks jmulvaney@library.umass.edu |