Feature #462
Feature #466: IPAACA v3
v3: Structured metadata
| Status: | In Progress | Start date: | 2015-03-26 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
To capture information such as publication or retraction / commission times, the existing metadata fields (flags etc.) are to be unified with the new ones into a single metadata structure, mirroring the payload structure.
Subtasks
History
#1
Updated by Ramin Yaghoubzadeh over 8 years ago
- Parent task set to #466
#2
Updated by Hendrik Buschmeier over 8 years ago
- Status changed from New to In Progress
I created a branch ipaaca3-dev (available here) that contains a first proposal for how the protobuf messages for ipaaca3 could look like (see 39a14c1d). In my proposal everything except `uid`, `mode`, `owner` and `revision` will be part of a general purpose metadata structure (`metadata`) that – on the protobuf message level – looks exactly as `payload` does.