| Documentation | Ingolf, all | - Collect (links to) documentation about data migration that we have written so far. → Mabye also/or alternatively do this in the DM Subgroup meeting
- What other areas of SysOps documentation do we want to see in the docs.folio.org site ?
- There is a little funding still available for funding projects, which may be used up in February of 2021. Dues for OLF will be going away this year, and we will need to make up that funding from other sources.
- Contributions to Folio are now voluntary. There is the hope that by lowering the barrier to entry, more institutions will hopefully be able to contribute more developer time.
- The Data Migration group has documentation in disparate locations, including proposals, code repos, workflow documentation coming from different legacy systems migrating to Folio. Dale proposed that they review those sources in a future Data Migration meeting, try to pull together the disparate links, and think about how they can be used to provide useful documentation for new-comers considering how to migrate their legacy data to Folio.
- Dale will invite Marsha to the meeting so that we can strategize about what kinds of data would be useful to collect and document. The root link for Folio documentation is at https://docs.folio.org/docs/getting-started/installation/
- Maybe the lack of migration tools is also a chance to get people aboaord who want to work on these migration tools.
- Jason shared an issue
OKAPI-969
-
Getting issue details...
STATUS
that would allow migrators to turn off timers so that notices to be loaded without actually sending out notices. Migration data used in testing situations can use bogus email addresses, but turning off timers will be useful for doing the actual migration.
- Jason: We should take the task to create a "Sysops contributions guide" on one of the next agendas.
|