ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAE
1
Assigned? YES or NOContact(s)InstitutionInstitution PriorityReportLegacy System Data Element SourcesFolio JIRA Issue(s)Is the report repeatedParameters to the reportRequires real-time data?PurposeLink to sampleImport/Export?NotesA-M NotesCanned ReportWithin-App
Cross-App
Cross-System
2
ID001NOAnne HighsmithTexas A&M, UA, Duke, OVGUP1 (TAMU); P4 (Duke);P1(UA); P1 (OVGU), P4 (Lehigh)Hathitrust submission projectsfull MARC bibliographic recordREP-5NoNoWhen TAMU participates in a digitization project to submit to Hathitrust, Hathitrust requires that a full MARC record be submitted for each item digitizedgeneralize the purpose of the reportExportHathi is a collaborative digitization project that many institutions participate. In practice, it operates much as a union catalog, thus the need for full MARC records. There is a robust API, that you can get info on here: https://www.hathitrust.org/bib_api. - Mike WinklerWe have not yet worked on export from FOLIO, so I don't have anything to add about this (yet), We will be working on it after Import is mostly completed. See UXPROD-652 for Data Export tool.
3
ID002NOAnne HighsmithTexas A&M, UA, Duke, OVGUP1 (TAMU); P2 (Duke); P1(UA), P1(OVGU), P5 (Lehigh)Ongoing authority control processingfull MARC bibliographic and authority recordsREP-6QuarterlyNoExtract records from database and submit them to authority control vendor so that bib record headings may be upgraded to RDA standards and authority records are updated to latest version. Updated MARC records are then reloaded into database.Export & ImportThis would be both Import and Export. The Import portion is in scope of what we're working on in the Data Import group. The Export portion is not. See UXPROD-652 for Data Export tool.
4
ID003NOSharon BeltaineCornell, UA, Duke, OVGUP1 (Duke); P1(UA); P1(CU), P1(OVGU), P1(Lehigh but need clarification)IMPORTS from a number of vendors: DeGruyter; Hart Pub Ebooks;Naxoos Music Lib and Jazz; Rand Ebooks; Alexander St Press; Coutts Approval and Patron Driven Print; Gale MARC Record Load; Marcive Load; Skillsoft Bks 24x7 Videos; Serial Solutions Journals and Ebooks; Early Arabic Printed Books; Vendoro Order Pickups; LCCairo Vendor Print Load; Yankeefull MARC bibliographic record; some purchase ordersREP-7regularlynoAdd records to Voyager databaseneed a lot of infomation about the various vendorsImportBibliographic records provided by vendors - M. Winkler
bibliographic data with additionl information about vendors; most likely financial transactional type of data - M. Winkler		This is in scope of the Data Import group. See list of record sources at https://wiki.folio.org/display/MM/Sources+of+Batch+Files cross-system
5
ID004NOSharon BeltaineCornell, UA, DukeP1 (Duke); P1(UA); P1 (CU), P1 (Lehigh but need clarification)EXPORTS: OCLC Daily Cataloging Export; Metadata List for RAPID and RAPID extract; WorldShare OCLC Manuscript-Archive Export; CRL Serials Extract; Daily Record Extract to OASIS; Monograph Holdings to Coutts Oasis; Hathi Trust Single and Multi-vol Monographs and HT Serials; OCLC WorldShare Daily Deletesfull MARC bibliographic record; metadataREP-8daily / regularlynoprovide required records to external vendorsExportReporting holdings to national bibliographic catalogues - M. WinklerWe have not yet worked on export from FOLIO, so I don't have anything to add about this (yet), We will be working on it after Import is mostly completed. See UXPROD-652 for Data Export tool.cross-system
6
ID005YESSharon BeltaineCornell, OVGUP1(CU)Usage Data from electronic content providersfull MARCX bibliographic recordREP-9regularlychange since date and timeyesProvide data for public facing discovery toolsexport; See Heather ShipmanIs this equal to COUNTER reports?We have not yet worked on export from FOLIO, so I don't have anything to add about this (yet), We will be working on it after Import is mostly completed.cross-system
7
ID006YESSharon BeltaineCornell, Duke, OVGUP1 (Duke); P1(CU), P1(OVGU), P2 (Lehigh)Invoice Control Report/Electronic Feedinvoice, fundREP-10dailyrun every day invoices are approvedYesInvoice Control report: gather financial data in total for all of the invoices approved the day before

Electronic Feed: sending by vendor, by invoice, by account number to university financial system to be paid (batch job)		Cornell categorizes these 2 reports as one because they 2 are versions of the same dataWe have not yet worked on export from FOLIO, so I don't have anything to add about this (yet), We will be working on it after Import is mostly completed. This has been identified as a need related to the Invoice module of Acquisitions.CornellInvoice Control Report/Electronic Feed
8
ID007YESClaudius HerktHamburg, OVGUP5 (H), P1(OVGU), P2 (Lehigh)COUNTER ReportsREP-11regularlyProvider, report type, report periodnomanage external Usage data in one placenot existent so farimportNot in the current scope of the Data Import group, which is only handling bibliographic and acquisitions data. Presumably, these would load to the ERM? ERMThe ERM subgroup has a ticket in Jira for support for importing COUNTER and other e-resource data
9
ID008NORob Pleshar (rpleshar@uchicago.edu)ChicagoP5 (UC), P2 (Lehigh)Usage data from electronic content providers combined with paymentsHARRASSOWITZ E-Stats/Payment data for the same subscription period in FOLIOREP-12regularlynomanage external Usage data in one placeimportCurrently almost all of our usage data is harvested by E-Stats. That includes billing information for those subscriptions already with Harrassowitz, but lacks the payment information for resources acquired from other sources.Not in the current scope of the Data Import group, which is only handling bibliographic and acquisitions data. Presumably, these would load to the ERM? Any MARC invoice or EDI invoice data IS in the scope of the Data Import group. yesERM/AcqThe ERM subgroup has a ticket in Jira for support for importing COUNTER and other e-resource data. See https://issues.folio.org/browse/UXPROD-576
10
ID009YESMichelle Paolillo, Sharon BeltaineCornellP1(CU)bibliographic submission for Google correctionsfull item-level MARC bibliographic recordREP-13yesProfile is documented at https://www.hathitrust.org/bib_specificationsyesWhen Cornell participates in a digitization project to submit to Hathitrust, Hathitrust requires that a full MARC record be submitted for each item digitized - see https://www.hathitrust.org/bib_data_submissiongeneralize the purpose of the reportExportHathi is a collaborative digitization project that many institutions participate. In practice, it operates much as a union catalog, thus the need for full item-level MARC records according to their spec.We have not yet worked on export from FOLIO, so I don't have anything to add about this (yet), We will be working on it after Import is mostly completed.perlscript in LSTools behind "Google" buttoncross-system
11
ID010YESMichelle Paolillo, Sharon BeltaineCornellP1(CU)Hathitrust bibliographic submission for new deposits and for correctionfull item-level MARC bibliographic record from individually specified recordsREP-14yesProfile is documented at https://www.hathitrust.org/bib_specificationsyesThe local partner catalog is considered the authoritative record for item deposits to HathiTrust. When there is an error in submitted metadata, practice is to correct the local catalog record, repackage and resubmit to Zephir (HathiTrust's metadata management system.) There are three reports that deliver similar output, but use different input and are named differently. ExportCornell has three production streams into HathiTrust, and a different routine for packaging each. (1) Google digitized items - identified by barcode, (2) locally digitized items - identified by barcode, (3) Kirtas/Microsoft digitized items, deposited to Internet Archive and identified by IA arkID. Barcode identified items rest in teh "coo" namspece and arkID identified items rest in the "coo1" namespace.We have not yet worked on export from FOLIO, so I don't have anything to add about this (yet), We will be working on it after Import is mostly completed.perlscripts in LSTools behind "Google" buttoncross-system
12
ID011YESMichelle Paolillo, Sharon BeltaineCornell, Duke, OVGUP1 (Duke); P1 (CU), P1(OVGU), P1 (Lehigh)not a report really, but need the ability to write my own reports as neededability to query our local instance of the hathifiles and unite this with our catalog dataREP-15yesneed access to hathifiles and our cataloging data in one interface so I might write my own reportsyesI often need to analyze large sets of material for sutability for deposit, and/or duplication of deposit, etc. I do this by writing MS Access queries that utilize our local Hathifiles instance and our catalog data as linked tablespaces in Access so I can get full information for the volumes, perfom analysis and derive spreadsheets for clients.ExportUsed for analysis for new deposits, cleaning up problems in previously submitted material
-(SMB) reporting functionality requirement?		??? Not sure how to respond to this oneMSAccess database linked to hathifiles and Voyager tablespacescross-system
13
ID012YESMichelle Paolillo, Sharon BeltaineCornellP2(CU)Processing steps for processing Google Candidate list into a picklistUnite local tables created from files from Google Return Interface and unite with current information to produce picklists and analysisREP-16yesneeds to be reasonably currentGoogle uses static catalog extracts that are out of date. To refresh locations to current ones, and to deduplicate among locations, and to exclude certain locations, locations must be reconciled and new picklists derived.ExportGoogle digitization is not curently active, but may restart if this becomes attractive.??? Not sure how to respond to this one
14
ID013YESMichelle Paolillo, Sharon BeltaineCornellP1(CU)HathiTrust Pre-deposit Display Preview ReportMARC 008 code for publication begin and end date, publication location, US Government doc; MARC LDR for bib format , BIB_ITEM, DISPLAY_CALL_NUM, author, title, publisherREP-17yesMARC 008 code for publication begin and end date, publication location, US Government doc; MARC LDR for bib format yesThe purpose is to predict the display behavior (full or limited view) of individual items and groups of items in HathiTrust prior to deposit. This report is also used to spot catalog issues and locate rights owners. It helps Cornell understand the amount of effort it will take to display an item in full view in the local library catalog prior to depositing it in the HathiTrust digital library. Overall, the report supports decision making by curators and collection stewards in determining the appropriate destination for collections migrations.ExportThe report mimics an algorithm used by HathiTrust to determine the viewability status of deposited digital materials. For more information, see: https://www.hathitrust.org/bib_rights_determination.We have not yet worked on export from FOLIO, so I don't have anything to add about this (yet), We will be working on it after Import is mostly completed.
15
ID014YESMichelle Paolillo, Sharon BeltaineCornell, DukeP4 (Duke); P2 (CU), P2 (Lehigh)HathiTrust Print Holdingslimited elements from MARC - see https://www.hathitrust.org/print_holdings REP-18yesprofile documented at https://www.hathitrust.org/print_holdings needs to be reasonably currentCornell annually delivers three print holdings statements (single volume monongraphs, multivolume monographs and serials). The statements include lost/withdrawn or missing items, as well as current holdings. These statements are the data source on which our annual fee is based, and also form the basis of the mechanism by which we can access preservation copies of withdrawn, lost or missing items that are in copyright. We have not yet worked on export from FOLIO, so I don't have anything to add about this (yet), We will be working on it after Import is mostly completed.
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100