Compare commits

..

No commits in common. "93ce37817031a1bd3278c57f1fdf22b56fe5e5ec" and "8bbdbeaeb9dee9cca32447b423bedb3021fe0283" have entirely different histories.

View File

@ -1,16 +1,5 @@
# Uploader to automate the Upload and Import of Objects in museum-digital via WebDAV # Uploader to automate the Upload and Import of Objects in museum-digital via WebDAV
The purpose of this app will be to allow museums to more simply automate the upload of
their collection data to museum-digital. It is thus targetted at museums using museum-digital
as a publication platform, while using another collection management system.
While collection management systems differ, an automatic import to museum-digital works in
a uniform way. Import data is uploaded via WebDAV, an import is configured using a text file. ([See here](https://de.handbook.museum-digital.info/import/importe-selbst-durchfuehren.html))
This part of the automatic importing can thus be solved in a one-fits-all solution here.
Collection management system-specific export scripts are necessary to present the present
app with data to upload. The export itself is thus out of the scope of the tool described here.
## Workflow ## Workflow
### Setup ### Setup
@ -80,7 +69,7 @@ It will hence attempt to do so when first run (or unless all relevant informatio
- `requests` / HTTP library - `requests` / HTTP library
- JSON parser - JSON parser
- XML parser (for version/update check) - XML parser (for version/update check)
- WebDAV client: [Python](https://pypi.org/project/webdav4/), [Golang](https://github.com/studio-b12/gowebdav) - [WebDAV client](https://pypi.org/project/webdav4/)
Either JSON or XML may also serve to store the config data. Either JSON or XML may also serve to store the config data.
@ -100,48 +89,3 @@ Either JSON or XML may also serve to store the config data.
- [ ] [musdb API: /user/read/{id}](https://gitea.armuli.eu/museum-digital/musdb/issues/1291) - [ ] [musdb API: /user/read/{id}](https://gitea.armuli.eu/museum-digital/musdb/issues/1291)
- [ ] [musdb API: /list_import_formats](https://gitea.armuli.eu/museum-digital/musdb/issues/1292) - [ ] [musdb API: /list_import_formats](https://gitea.armuli.eu/museum-digital/musdb/issues/1292)
## Potentially Interested Parties
- Landesstelle Sachsen (unsure, via @szunkel)
- Staatliche Schlösser und Gärten Hessen (EasyDB, via @ufladerer)
## Misc.
### Useful Links
- [Cross-Compiling Golang Sources](https://opensource.com/article/21/1/go-cross-compiling)
### Connection to Local Collection Management Systems
#### Axiell Collections
?
#### BeeCollect
?
#### EasyDB
EasyDB has a feature for automating exports and usually comes with a built-in image server.
Esp. if the image server is publicly accessible, the requirements for automating imports to
md (automated, scheduled export to a directory) are thus available in the app without the
need for an additional connector.
#### Faust
?
#### FirstRumos
?
#### Hida
?
#### MuseumPlus
- Current Version has an API, a connection to it could be built upon that.