dustymc
commented
3 months ago One small technical problem: The Universe, like many things which do not exist, ain't very sticky and the barcodes keep falling off!
We should probably talk about the techy-bits of the model at some point, some of which were inherited from Oracle and could probably be different for PG, but until then:
There truly is no container zero, just a loophole in the constraints to allow new containers to be - uhh, somewhere, or nowhere, or whatever that is.
There's also VPN control on the table now, so I suppose that technically it's a multiverse - there are...
arctosprod@arctos>> select count(distinct(institution_acronym)) from container;
count
-------
54fifty-some-odd universes - or would be if they actually existed, or something.
Anyway, no place to stick barcodes.
Your solution is the proven one (and I think UAM already owns a barcode=0).
indicate that it is lost
... or newly created, or.... or ... or..... If you want to indicate something's lost, I would VERY highly recommend creating a (or a few) "things that are lost" container(s) for them.
I can (I think, never tried!) update containers to be in the thing which doesn't exist, that could probably somehow be added to the UI, but it's still going to be hard to barcode.
camwebb
Newly minted, barcoded containers have 'The Universe' as their parent (
container.parent_container_id= 0), by default. Once they have been moved into another container, I can see no way to move them back to have 'The Universe' as their parent, since The Universe itself (container.container_id= 0) does not appear to exist ( :wink: ) and has no barcode. It would be helpful to be able to return a container to The Universe to indicate that it is lost. The alternative, creating a special 'lost' container, is of course easy and possible, but not as clean. The return a container to The Universe a barcode will be needed ("0"?).(Related to ArctosDB/arctos#4547)