Welcome to the FOLIO Wiki
Spaces
Apps
Templates
Create
Folio Development Teams
All content
Space settings
Shortcuts
How-to articles
How-to articles
This trigger is hidden
Retrospectives
Retrospectives
This trigger is hidden
Meeting notes (2)
Meeting notes (2)
This trigger is hidden
Product requirements
Product requirements
This trigger is hidden
File lists
File lists
This trigger is hidden
Content
Results will update as you type.
Meet the teams:
Aggies
•
aleph2folio team
Benevolence
•
Bienenvolk (former: ERM Team)
•
Citation Team
Core Platform team
Eureka Team
Firebird Team
Folijet Team
FOLIO DevOps
Gutenberg (Mainz) Team
Kitfox Team DevOps - Dev Support
Leipzig Team
MOL team
•
Mriya Team (AQA)
•
National Library of Australia (NLA) Team
Odin (Hebis) Team
Performance Task Force Team
Prokopovych Team - Deprecated
Sif (GBV) Team
Sinopia Team
Spitfire Team
•
Spitfire - Definition of Done v2.0
•
Spitfire - Jira Flow
•
Spitfire - Issue priorities
Spitfire - Retrospective / Action Plan
Spitfire - Spikes/Investigations
quickMARC
Data Import
MARC records investigation
•
Data-import testing approach on Rancher
•
MARC Holdings - Default Mapping profile
•
SPIKE: Ability to delete an authority record
•
Spike: MODDATAIMP-361 Investigation: Import MARC Authority records
•
Spike: MODDICORE-169 Import Holdings - Define changes needed to maintain Holdings creation
•
Spike: MODSOURCE-274 Store MARC Holdings record
•
SPIKE: MODSOURMAN-526 Verify persist value in DB during parsing 004 field
•
SPIKE: MODSOURMAN-623 Authority record > Generate a 999 ff $i
SPIKE: Searching MARC Authority Records via MARC authority app
•
SPIKE: Update MARC authority records via Data import
•
Spike MODDATAIMP-420 - Create monitoring task for Data Import app
•
Spike: MODQM-75 - Investigate | MARC Authority record | Implement sequence number generation mechanism for HRIDs
•
Spike: SPIKE: Data Import Component: Investigate an approach to move backend file upload functionality into a separate java library
MARC Search API
eHoldings
Custom Fields
Notes
Load Testing
Other
Search
Entities-links
Spitfire - Tips and how-tos
MARC Resources
MARC Features
Feature Testing
Spitfire - Documentation
Open Search
Spitfire - Archive
•
Product Owner - Cataloging - Things to know
•
Inventory modules transition
Spitfire - Features
•
Multiple (alternate) Graphic Representations - Notes
•
Metadata Management : Ramsons UAT Schedule
Stripes-Force team
Team Bama
Teams archive
Thor (Index Data)
Thunderjet (ACQ) Team
•
UNAM Team
Vega Team
Volaris Team
Corsair Team
Dreamliner
•
Nighthawk Team (MetaDB improvement team)
Bloom team
Engineering Process
Testing
How-to articles
•
Newcomer's first steps
•
marc4j overview
•
OKAPI request dispatching and interface types overview
•
Chained futures and rx-java overview
•
Development tips and notes
Suggestions for code improvement
•
Scrum Master - Onboarding tips
•
Data Import performance of retrieving source records
Data-import user guides
•
PostgreSQL JSONB is not for free
Retrospectives
•
Meeting notes (2)
•
Developer questions about libraries
•
[Draft] Baseline DoD
•
UI Peer Review duties plan
•
Product requirements
•
File lists
•
Data Import Roadmap: Ramsons, Sunflower, & beyond
Apps
draw.io Diagrams
Folio Development Teams
/
/
MARC records investigation
/
MARC Holdings - Default Mapping profile
Summarize
MARC Holdings - Default Mapping profile
Natalia Zaitseva
Owned by
Natalia Zaitseva
Last updated:
Aug 19, 2021
66 min read
Loading data...
Natalia Zaitseva