Project

General

Profile

Actions

Idea #21844

open

add file_properties column for per-file metadata in a collection

Added by Peter Amstutz 4 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
API
Target version:
Start date:
Due date:
Story points:
-

Description

https://www.postgresql.org/docs/current/datatype-json.html

Since Postgres 12, JSON path queries can dig into JSON structures and can be indexed. This should give us a path to implementing per-file properties on collections that can be queried.

Investigate and propose a detailed design for per-file metadata.

Actions #1

Updated by Peter Amstutz 4 months ago

  • Description updated (diff)
Actions #2

Updated by Peter Amstutz 4 months ago

  • Description updated (diff)
Actions #3

Updated by Peter Amstutz 4 months ago

  • Target version changed from Development 2024-07-24 sprint to Development 2024-08-07 sprint
Actions #4

Updated by Peter Amstutz 4 months ago

I want to think about this one a bit. I think there's a couple ways to approach about this. One is tagging of individual files, which is what we've sketched out here.

Another another approach would be to design a more general table model for metadata -- a primary key (sample id / patient id or whatever) and a number of fields, which can include references to files.

As a data scheme, it needs to reasonably efficient for browsing in workbench, and basic filtering (ideally should be able to efficiently look up by any field).

Actions #5

Updated by Peter Amstutz 3 months ago

  • Target version changed from Development 2024-08-07 sprint to Future
Actions #6

Updated by Peter Amstutz 3 months ago

  • Target version changed from Future to Development 2024-08-28 sprint
Actions #7

Updated by Peter Amstutz 3 months ago

  • Target version changed from Development 2024-08-28 sprint to Future
Actions

Also available in: Atom PDF