Migration and Curation tools #93

New issue

Open

opened 2025-07-09 14:39:15 +00:00 by christian-monch · 1 comment

christian-monch commented

2025-07-09 14:39:15 +00:00

(Migrated from github.com)

With the option for multiple backends, a few questions arise. This issue is created to identify the questions and to discuss them

Q1: How can an existing deployment with backend A move to backend B?
Q2: What kind of tools are required to support curation workflows, especially when a backend does not have an easy-to-read file-system-based data structure?

With the option for multiple backends, a few questions arise. This issue is created to identify the questions and to discuss them - Q1: How can an existing deployment with backend A move to backend B? - Q2: What kind of tools are required to support curation workflows, especially when a backend does not have an easy-to-read file-system-based data structure?

christian-monch commented

2025-07-25 07:53:18 +00:00

(Migrated from github.com)

Answer to question Q1:

Version 2.0.0 introduced the new command:

dump-things-copy-store

This command can be used to copy records from one backend to another backend. For example, it can be used to copy records from a directory-based backend (record_dir) to an SQL backend, e.g., sqlite.

Answer to question Q1: Version 2.0.0 introduced the new command: ``` dump-things-copy-store ``` This command can be used to copy records from one backend to another backend. For example, it can be used to copy records from a directory-based backend (`record_dir`) to an SQL backend, e.g., `sqlite`.