Structured metadata for documents #2770

Closed
opened 2015-04-27 16:52:10 +00:00 by wjt · 2 comments

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.

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.
wjt added the
general
label 2015-04-27 16:52:10 +00:00
wjt added this to the 14.04 milestone 2015-04-27 16:52:10 +00:00
0x2620 was assigned by wjt 2015-04-27 16:52:10 +00:00
wjt added the
normal
defect
labels 2015-04-27 16:52:10 +00:00
Author

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.)

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.)
Owner

documents can have structured data now. via documentKey in config

documents can have structured data now. via documentKey in config
j added the
fixed
label 2018-09-19 10:27:12 +00:00
j closed this issue 2018-09-19 10:27:12 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: 0x2620/pandora#2770
No description provided.