artefactual / artefactual/atom

Enhancement: Support for hierarchical structure in physical storage module

Open
#2,185 0 comments 1 reaction 0 assignees View on GitHub
Type: enhancement
Dominant language
PHP
Stars
297
Forks
152
Avg merge
1d 8h
Merged PRs (30d)
3

Description

Although the Physical Object Type taxonomy is hierarchical, both the data table on the "Browse Physical storage" page (found under Manage > Physical storage) and the [physical storage reports](https://accesstomemory.org/en/docs/2.10/user-manual/reports-printing/create-physical-storage-report/#storage-report-view) are flat and unordered. This makes it difficult to discern how large a container is and how many sub-containers/boxes/folders (etc.) it might contain. This limits AtoM's ability to model real-world physical storage configurations accurately. It also means that users also can't trace the physical lineage of an item stored with a nested container.

**Possible solutions**:

- Display physical storage containers on the browse page and in reports with parent-child relationships and nested levels.
- Add a breadcrumb trail for nested levels and related resources so that you can always see where you are in context of the other records in that containers.

AtoM version: 2.9.2

Contributor guide

Open the contributing guide

Research direction

Start at Manage > Physical storage and inspect the Browse Physical storage page, then review the linked physical storage reports. Compare how containers are currently displayed and ordered; done means both views show parent-child nesting and provide breadcrumb context for nested levels and related resources.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.