Discovery and/or creation of Eresources (UXPROD-577)

[UXPROD-1514] Import resources from KBART files Created: 30/Jan/19  Updated: 16/Sep/20  Resolved: 18/Mar/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2020
Parent: Discovery and/or creation of Eresources

Type: New Feature Priority: P3
Reporter: Owen Stephens Assignee: Owen Stephens
Resolution: Done Votes: 0
Labels: entitlements, erm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by ERM-685 Support import and processing of KBAR... Closed
Relates
relates to ERM-299 Filter e-resource packages by source Closed
relates to UXPROD-1465 Import resources from JSON files Closed
relates to UXPROD-1513 UI for file import of resources (pack... Closed
relates to ERM-481 Support Edition information in Agreem... Closed
relates to ERM-482 Support Author information in Agreeme... Closed
relates to ERM-485 Support e/p monograph publication dat... Closed
relates to ERM-486 Support monograph volume in Agreement... Closed
relates to ERM-676 Support Editor information in Agreeme... Closed
Requires
requires UXPROD-2081 Management and display of non-serial ... Closed
Epic Link: Discovery and/or creation of Eresources
Development Team: Bienenvolk
PO Rank: 15
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R3
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R2
Rank: Hungary (MVP End 2020): R2
Rank: Lehigh (MVP Summer 2020): R4
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R5

 Description   

Support the import of csv or tsv files conforming to the KBART Phase II Recommended Practice (https://groups.niso.org/apps/group_public/download.php/16900/RP-9-2014_KBART.pdf) to create resources (packages/titles) for ERM

Using package_name and package_id as specified in the KBART Automation recommended practice (https://www.niso.org/publications/niso-rp-26-2019-kbart-automation) could provide a way of matching to a package in Folio

Otherwise we may need to fall back on using the filename which (according to the KBART Phase II doc) should use the pattern:
[ProviderName][Region/Consortium][PackageName]_[YYYY-MM-DD].txt

6.5.1 The file should be entitled:
[ProviderName][Region/Consortium][PackageName]_[YYYY-MM-DD].txt

“Region/Consortium” should include any information based on where the package is sold, or to what consortium it applies. If the file is for a universal list, “Global” should be used.

Examples:
Title list is not region or consortium-specific, includes all titles from the content provider:
• JSTOR_Global_AllTitles_2013-01-14.txt
• TaylorandFrancis_Global_AllTitles_2012-08-30.txt Title list is consortium-specific, for a specific package:
• IOP_NESLi2_Option1-2011_2012-05-31.txt (includes a year as part of the package name)
• OxfordJournals_SCELC_AllTitles_2013-01-09.txt (contains all titles that the consortium has subscribed to)

Title list is region-specific, for a specific package:
• Springer_Asia-Pacific_Medicine_2013-01-28.txt

6.5.2 The provider name should be the platform at which the data is hosted (but without the
punctuation).
This ensures that one provider’s data is clearly distinguished from data provided by others with similar package names. Also, the file name should be consistent for each metadata file deposited.

Publishers and vendors should avoid using special characters in filenames. Both upper and lower case characters are allowed as long as the content provider is consistent in its filenames throughout cycles of transmission.

Examples:

  • Oup_Highwire_AllTitles_2013-01-09.txt
  • Bloomsbury_IngentaConnect_Alltitles_2013-01-01.txt

6.5.3 Separate files should be produced for each package of content that the provider offers. Files should be named as customers would expect to see them labeled in the knowledge base, using the syntax:
[ProviderName][Region/Consortium][PackageName]_[YYYY-MM-DD].txt

Example:

  • JSTOR_Global_ArtsandSciencesV_2013-01-14.txt

Providers and recipients can agree in advance how best to present complex package names.

Should integrate with a UI (see UXPROD-1513 Closed ) so users can import a file following KBART practice from within a Folio UI



 Comments   
Comment by Theodor Tolstoy (One-Group.se) [ 08/Feb/19 ]

Chalmers would do this in eHoldings/HLM? Khalilah Gambrell

Owen Stephens this one might need a couple of tags.

Comment by Khalilah Gambrell [ 08/Feb/19 ]

Theodor Tolstoy (One-Group.se) - not applicable to any library using eholdings/HLM.

Comment by Anya [ 16/Oct/19 ]

FC : THis would be GREAT for Eholdings. is there anything in the works for that?

Comment by Khalilah Gambrell [ 16/Oct/19 ]

Anya, not at this time. I have been thinking about it as it can address several requests but I need my team to do some research.

Comment by Anya [ 16/Oct/19 ]

Khalilah Gambrell Good to know!

jmulvaney@library.umass.edu for your information

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