manage the hierarchical relationships of an archival unit in the > relatively flat, table-like structure of the MySQL database. Sometimes, > this nested set can get corrupted

for the hierarchical arrangement of containers and locations - ie placing a box on a shelf, nesting a shelf on a row or bay, placing that row in an aisle, then a room, etc. If we give those

Thanks again Dan - yes I think they're going to manually correct the issue re the space between the alpha and numeric elements. Will let you know

>> hierarchical and so am now stuck with a bunch of unrelated objects in “File >>>>>>>> 1”, for example, even though they're in different boxes

t any hierarchical linking between Types of > physical storage, for instance *store *and more specific type of physical > storage (for example *row-bay-shelf *combination

such as hierarchical organization, and more) to make this a very practical alternative without some careful container naming and usage conventions set up in advance. In the meantime

have no hierarchical > organization), many of your file level containers will end up in the same > big bucket. What I mean is, on the archival description you'll have 2 >

Hi everyone! I am having trouble wrapping my head around the physical storage taxonomy. I am used to