Feature Request - a way to un-containerize a barcode?

[DerekSikes]

Issue Documentation is http://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html

Is your feature request related to a problem? Please describe.

Is there a way to remove a barcode from its container?

Currently, if a barcode is in the wrong container and we are waiting to scan it into its correct container I think best practice is to move it to barcode 0 (mammals parentless void) but it would be more elegant to just return it to container-less status (as it was when it was born).

Describe what you're trying to accomplish Sometimes I re-use barcodes for specimens that have been deleted, or grab a unit tray that had been inside a drawer (and Arctos thinks is still inside a drawer). I'd like to be able to re-set the container of that barcode to null until we get around to properly scanning it into its actual container.

Describe the solution you'd like Find container -> edit this container -> button that says "change parent container to NULL" or something

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Using mammals container 0 "parentless void"

Priority Please assign a priority-label. Unprioritized issues gets sent into a black hole of despair. medium

[Jegelewicz]

grab a unit tray that had been inside a drawer (and Arctos thinks is still inside a drawer)

IMO - the unit tray should get scanned into whatever room it is sitting in. Putting it "nowhere" means that the data do not reflect reality and the box is effectively missing or the barcode is no longer on the unit tray.

[DerekSikes]

That's a good idea! I know I've done that in the past... thanks!

On Tue, Apr 12, 2022 at 10:19 AM Teresa Mayfield-Meyer < @.***> wrote:

grab a unit tray that had been inside a drawer (and Arctos thinks is still inside a drawer)

IMO - the unit tray should get scanned into whatever room it is sitting in. Putting it "nowhere" means that the data do not reflect reality and the box is effectively missing or the barcode is no longer on the unit tray.

— Reply to this email directly, view it on GitHub https://github.com/ArctosDB/arctos/issues/4547#issuecomment-1097044343, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACFNUM6RJI5STXYCJOLXFCDVEW5DLANCNFSM5TIEI2VA . You are receiving this because you authored the thread.Message ID: @.***>

--

+++++++++++++++++++++++++++++++++++ Derek S. Sikes, Curator of Insects, Professor of Entomology University of Alaska Museum (UAM), University of Alaska Fairbanks 1962 Yukon Drive, Fairbanks, AK 99775-6960 @.*** phone: 907-474-6278 he/him/his University of Alaska Museum https://www.uaf.edu/museum/collections/ento/

• search 357,704 digitized arthropod records http://arctos.database.museum/uam_ento +++++++++++++++++++++++++++++++++++

Interested in Alaskan Entomology? Join the Alaska Entomological Society and / or sign up for the email listserv "Alaska Entomological Network" at http://www.akentsoc.org/contact_us

[campmlc]

Currently I have to do this by moving the part to a parentless void and deleting the barcode, then I re-create the barcode as a label using "Create Container (evil)".

On Tue, Apr 12, 2022 at 12:16 PM DerekSikes @.***> wrote:

• [EXTERNAL]*

Issue Documentation is http://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html

Is your feature request related to a problem? Please describe.

Is there a way to remove a barcode from its container?

Currently, if a barcode is in the wrong container and we are waiting to scan it into its correct container I think best practice is to move it to barcode 0 (mammals parentless void) but it would be more elegant to just return it to container-less status (as it was when it was born).

Describe what you're trying to accomplish Sometimes I re-use barcodes for specimens that have been deleted, or grab a unit tray that had been inside a drawer (and Arctos thinks is still inside a drawer). I'd like to be able to re-set the container of that barcode to null until we get around to properly scanning it into its actual container.

Describe the solution you'd like Find container -> edit this container -> button that says "change parent container to NULL" or something

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Using mammals container 0 "parentless void"

Priority Please assign a priority-label. Unprioritized issues gets sent into a black hole of despair. medium

— Reply to this email directly, view it on GitHub https://github.com/ArctosDB/arctos/issues/4547, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADQ7JBGLGWTGKJAAFPYZILLVEW4ZDANCNFSM5TIEI2VA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[dustymc]

I think this needs more discussion, there seems to be a few things going on.

parent==0 ("the universe") is IMO best reserved for containers which haven't been in the system, but I think I can allow explicitly returning containers to parent zero if necessary. Recycling a barcode seems like a great way to add confusion eg if the history comes along - do we need some sort of "hard reset" option, rather than just updating the location, and what would that mean for the history of former children?

Definitely agree with keeping containers in whatever's known when possible.

[campmlc]

The current alternative is to delete the barcode and then recreate it as as a label in the universe. A lot of trouble, and potentially breaking more things than decontainerizing it. I have to do this fairly regularly.

On Tue, May 3, 2022, 9:50 AM dustymc @.***> wrote:

• [EXTERNAL]*

I think this needs more discussion, there seems to be a few things going on.

parent==0 ("the universe") is IMO best reserved for containers which haven't been in the system, but I think I can allow explicitly returning containers to parent zero if necessary. Recycling a barcode seems like a great way to add confusion eg if the history comes along - do we need some sort of "hard reset" option, rather than just updating the location, and what would that mean for the history of former children?

Definitely agree with keeping containers in whatever's known when possible.

— Reply to this email directly, view it on GitHub https://github.com/ArctosDB/arctos/issues/4547#issuecomment-1116255530, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADQ7JBCAOOA4NKHRBT7CNKLVIFDLHANCNFSM5TIEI2VA . You are receiving this because you commented.Message ID: @.***>