-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the scope of in place import more explicit (edits) #5
Conversation
--transfer=cp is copy but also in-place.
@@ -4,7 +4,7 @@ In-place import | |||
=============== | |||
|
|||
In-place import allows files which are already present on the server machine | |||
to be imported into OMERO without the need to copy them into OMERO's ManagedRepository. This requires |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be a question for @fmeyenhofer. He added this specifically trying to get something across.
|
||
Do not use soft links when pointing to data inside the | ||
ManagedRepository. If the originals are deleted, the data will be | ||
lost. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the piece of information was missing for me. Good idea to add it.
@@ -4,7 +4,7 @@ In-place import | |||
=============== | |||
|
|||
In-place import allows files which are already present on the server machine |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rephrasing: In-place import allows image files that are accessible from the OMERO.server's filesystem...
(because they do not have to be stored on the server machine, but can be on any machine if mounted into the servers FS)
Merging to update the commit. |
Just a couple of thoughts for you to cherry-pick or merge as you like.