Rewrite Cornell's Web based LS-Tools (UXPROD-949)

[UXPROD-950] Rewrite Cornell's Web based LS-Tools Created: 14/Jun/18  Updated: 18/Apr/23  Resolved: 18/Apr/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Rewrite Cornell's Web based LS-Tools

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: data-import, sysops_mgt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Rewrite Cornell's Web based LS-Tools
Front End Estimate: XXL < 30 days
Front End Estimator: Chris Manly
Front-End Confidence factor: Medium
Back End Estimate: XXL < 30 days
Back End Estimator: Chris Manly
Estimation Notes and Assumptions: Going with XXL for both front and back and at this point is probably about right. It's not going to be smaller than that. In the details, I think there will be a lot of "it depends on how other related pieces are done" but fundamentally there's a sizeable chunk of work to be done.
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R5
Rank: 5Colleges (Full Jul 2021): R5
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R5
Rank: hbz (TBD): R5
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R5

 Description   

LS-Tools = A tool set at Cornell which allows technical services do library automation tasks through a common web interface.
It is essentially an ETL tool. It comprises cleanup jobs, export and import jobs. There is a specification written for each job that describes who owns it, how it is executed, what is needed, etc. The app also allows for searching of marc data with a highly granular selection capability. The app is a swiss army knife of technical services activities. It has meant a huge increase in productivity for technical services staff. Reimplementing this in Folio will be a challenge.
Some combination of the workflow engine and the marc batch loader could replace LS tools. The workflow engine is meant to be a platform to build these kinds of applications on.



 Comments   
Comment by Cate Boerema (Inactive) [ 27/Jun/18 ]

Ingolf Kuss, Tod Olson We need to get rough dev estimates on this by EOD today and our developers don't feel like they understand this well enough. Is there someone at Cornell who might be able to do it for us? These are meant to be t-shirt size estimates (just SWAGs), so it shouldn't take long for someone who understands this tool.

Please just have them edit this issue and populate the Front End Estimate and Back End Estimate fields and add their name as Front End Estimator and Back End Estimator.

If we don't get a better estimates today, we'll have to give this XXL for both front and backend.

Thanks much!

Comment by Ingolf Kuss [ 27/Jun/18 ]

Chris Manly, can you do the estimate ?

Comment by Tod Olson [ 27/Jun/18 ]

I just Slacked with Chris Manly, he will try to look at it tonight.

Comment by Chris Manly [ 27/Jun/18 ]

Going with XXL for both front and back and at this point is probably about right. It's not going to be smaller than that. In the details, I think there will be a lot of "it depends on how other related pieces are done" but fundamentally there's a sizeable chunk of work to be done.

(I don't have permissions to edit this issue directly, so I can't populate the estimation fields.)

Comment by Anya [ 29/Mar/19 ]

Comment from the March Meeting : would need to understand the functionality better; how applicable to non-Voyager libraries? Is this served by other FOLIO tools?

Comment by Erin Nettifee [ 17/Apr/23 ]

Thomas Trutt does this need to stay open?

Comment by Thomas Trutt [ 18/Apr/23 ]

Erin Nettifee it can be closed. thank you for checking. 

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