Request - New Container UI #8890
Description
I propose a new container UI:
- similar search capacity to https://arctos.database.museum/findContainer.cfm
- results returned in a tabular format similar to /info/container_contents.cfm ("Container Contents" link from container search results), but
- more columns-sets (tentatively 10)
- less-cryptic headers (container_thing_x instead of BCX, LBLX, TX, CIDX)
- part(s) split out into a predictable column (if I can figure out how, ideally on the far left - but whatever UI I use for this might allow column order shuffling anyway); see https://docs.google.com/document/d/1on0bbE7Z21YycA0CDeuyDmky96GW72ZcxpeMga29h2Y/edit?tab=t.0#heading=h.39xol5jj1q66 for Object Tracking WG discussion of this topic)
- data assembled serverside, so it can potentially be downloaded in large chunks even without a more-performant front-end (https://github.com/ArctosDB/internal/issues/376) and possibly paginated in the UI
If this works, it would be expected (not necessarily immediately) to replace https://arctos.database.museum/findContainer.cfm (because https://github.com/ArctosDB/BackBurner/issues/14), /info/container_contents.cfm ("Container Contents" link from container search results, because it would contain all that information plus some), and probably some other stuff - this would (if it doesn't have some unforeseen functional limitation) become the primary container UI, and we would deprecate and eventually remove anything that significantly overlaps it.
One unaddressed hopefully-theoretical concern: This would not be a suitable primary UI for anyone who's using more hierarchical depth than can readily be squished into the proposed fixed-width structure. That is not a metric that's easy for me to find, so please let me know if you are using hierarchies with more than ~a dozen levels.
Issues to close:
- Request - Async download of container contents #8819 (this would directly provide a more-useful data package, and assemble it in a fashion more suitable for download)
- Proposed new tool: download container contents maintaining hierarchy for large datasets #8731 (same as above)
- Request - Make "CSV for scary barcode swapper" ignore position #8709 (this would provide consistently-labeled - plus or minus a
{_int}bit - data which could be fed to other container-related tools)
Request - Update container contents layout to have more specific headers #8110 (this would provide clarity and consistency in headers)
CSV search of list of barcodes #6056 (this would break our ties to an old and fragile library and allow more responsive development)
@happiah-madson @falco-rk @mkoo lemme know what I missed or got wrong.