Add some additional documentation about record ownership during import #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NicolasCARPi
requested changes
Sep 13, 2024
| @@ -75,6 +75,13 @@ Figure out the Team ID by looking at the Team from the Sysconfig panel, where th | |||
| # import in team 42, force everything to be of type "Resources" with category "6" | |||
| docker exec -it elabftw bin/console import:eln --type items --category 6 your.eln 42 | |||
|
|
|||
| By default (if no ``--userid`` setting is provided), the ownership of the items will be | |||
| determined by comparing the email addresses of users between the export and import | |||
| servers. This allows for simple migration of data from one ELabFTW server to another, | |||
There was a problem hiding this comment.
make sure to use correct case: eLabFTW
| By default (if no ``--userid`` setting is provided), the ownership of the items will be | ||
| determined by comparing the email addresses of users between the export and import | ||
| servers. This allows for simple migration of data from one ELabFTW server to another, | ||
| even if users have differing ``userid`` values on the two servers. If the user that owns |
There was a problem hiding this comment.
I'd prefer "instance" instead of "servers". Or maybe both "instances/servers".
| servers. This allows for simple migration of data from one ELabFTW server to another, | ||
| even if users have differing ``userid`` values on the two servers. If the user that owns | ||
| an item in the exported data is not present on the destination (import) server, the | ||
| importer will create users as necessary. |
There was a problem hiding this comment.
"importer" could be replaced by "import process", to make it cleare we're talking about the code, not the human doing the import.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.