Specify dates schema when dealing with Legacy Software
When the deposit contains software that was written many years ago but is encapsulated in a container that was created today, dating the content is tricky. Here an example of the artifacts we receive in a deposit:
- metadata in xml - zipped archive - Scilab 1.1 - README - AUTHORS - LICENCE - src [legacy content]
src directory contains content created in 1980 while the root directory contains data created in 2019.
The idea is the following,
- create 1 revision A only with
srccontent dated to 1980 with the extracted metadata in
- create 1 revision B with the complete deposit
deposit_dateextracted from SWORD protocol when deposit is received.
- B points to A
- create 1 revision C for
- create 1 revision D for complete deposit
- C points to A
- D points to B
- C points to D
A (1980) -----------C (1981) / / B (2019)-----------D(2019)
We need also to consider creating a branch for the
synthetic_history (A+ C)
And see how we specify exactly which content is legacy inside the deposit itself.
Migrated from T1897 (view on Phabricator)