Difference between revisions of "Imeji version management"
Jump to navigation
Jump to search
(Created page with "== Status == * Not implemented * '''Nb: The version metadata are available, but the version management is not implemented yet in imeji''' == use cases == The version managemen...") |
|||
| Line 21: | Line 21: | ||
== Technical description == | == Technical description == | ||
* the version management is implemented via the [[imeji/properties | * the version management is implemented via the [[imeji/properties imeji_properties]] | ||
Revision as of 07:37, 24 April 2012
Status
- Not implemented
- Nb: The version metadata are available, but the version management is not implemented yet in imeji
use cases
The version management uses the following model (inspired by the dublin core schema).
| version | hasVersion | replaces | created | issued |
|---|---|---|---|---|
| 1 | domain/object/123/1 | - | 01/01/2000 | 01/06/2000 |
| 2 | domain/object/123/2 | domain/object/123/1 | 01/01/2001 | 01/01/2002 |
| 3 | domain/object/123/3 | domain/object/123/2 | 01/01/2002 | - |
Note:
- When an object is released, it gets a date issued. The next version is created only when used wants to revise/modify the last released version.
Technical description
- the version management is implemented via the imeji/properties imeji_properties