artefactual / artefactual/atom

Problem: Only select metadata fields can be hidden from unauthenticated users

Open
#2,282 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
PHP
Stars
297
Forks
152
Avg merge
1d 8h
Merged PRs (30d)
3

Description

**Issue**

Within the "Visible elements" module, each data entry template's "Elements" section only contains a list of select metadata fields which can be hidden from public users. If so inclined, admins should be able to hide _all_ possible metadata fields.

e.g., "Location of originals" field in RAD template might include physical storage information + additional metadata that admins want to hide from unauthenticated users but want authenticated users to see it.

nb: Could also be filed as a docs issue: specific fields that _can't_ be hidden based on AtoM's current functionality could at least be explicitly outlined (perhaps under each information area) in the product documentation to avoid any user confusion.

**Existing workaround(s)**

- Move affected metadata to another appropriate field included in the list of template elements (e.g., "General note(s)" if applicable) - Potential problem here, though, is that the fields admins want to hide might not fit within other fields based on the rules/conventions of the chosen standard )
- Switch affected description(s) to "Draft" publication status - Can only be a temporary measure unless unauthenticated users don't need access to those descriptions
- Set group permissions for "anonymous" to READ | DENY for affected descriptions - Again, likely only a temporary measure

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the “Visible elements” module and the “Elements” section of each data entry template, using the RAD template’s “Location of originals” field as the concrete example. Confirm which metadata fields are currently available for unauthenticated-user visibility controls; done means admins can hide any applicable field from public users while authenticated users can still see it, or the documentation clearly lists fields that cannot be hidden.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
authorization, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.