Structured metadata for documents #2770
Labels
No labels
backend
critical
defect
duplicate
enhancement
fixed
frontend
general
invalid
major
minor
normal
oxjs
pandora_client
python-ox
task
trivial
wontfix
worksforme
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: 0x2620/pandora#2770
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
At present, documents have a title, a description, and (https://code.0x2620.org/0x2620/pandora/issues/2818 aside) a set of entities. It would be useful to have other fields – in particular, a date (which would not be the same as the upload date, or the EXIF date in the case of a photo) – just like is possible for footage.
Perhaps the ontology could be shared, so a document can be tagged with the same years, themes, etc. as footage is.
Somewhat related to https://code.0x2620.org/0x2620/pandora/issues/2597 I suppose. It's true that arbitrary data could go in the description field and (hypothetically) be searched from there but that seems inconsistent with the structured-metadata model of the rest of pan.do/ra.
For what it's worth, I worked around this limitation in the instance here by creating a new entity type, "phototags", and representing eg. years as phototags entities named something like "Year: 1958". (Also I made themes into entities, for unrelated reasons.)
documents can have structured data now. via documentKey in config