Design question about original_user and original_group
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing where the original_user and original_group metadata are populated, then compare the OMERO session values with the object owner on the origin server. Confirm the intended semantics with maintainers before changing behavior, and verify that transfer metadata records the agreed ownership values.
Written by the indexing model from the issue text.
Description
As currently implemented, the metadata original_user and original_group are taken from the omero session which is not very informative. I was expecting it to store the user/group that own the object on the origin server instead. I wanted to verify what the intent was before submitting a patch that changes it to the latter.
- Dominant language
- Python
- Stars
- 19
- Forks
- 20
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ome/omero-cli-transfer
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
ome/omero-cli-transfer#117 · 5 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ome/omero-cli-transfer#121 · 7 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
ome/omero-cli-transfer#88 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
ome/omero-cli-transfer#83 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ome/omero-cli-transfer#69 · 8 comments · 1 reaction ·
All issues in ome/omero-cli-transfer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
comp/desktop P3 type/feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#154285 ·
Maintainers usually reply within 1 day
-
docs: qualify copied and custom kubectl debug policy notesPossibly taken @nym01 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kubescape/cel-admission-library#166 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
SACGF/variantgrid#2804 · 1 comment ·
Maintainers usually reply within 1 day
-
[BUG] HTTP lifecycle dispatch treats a NO_PROXY-only environment as corporate egress and skips the resolve-and-pinned sessionPossibly taken @bodapatisaikrishna claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day