search

Automatic-Ingest-Digital-Archives / SCALA

4 stars 1 forks source link

No AIP versioning using version tag #56

Open JelleKleevensVAI opened 3 years ago

JelleKleevensVAI commented 3 years ago

image

WimLo commented 3 years ago

Information from the mail conversation:

Hello Ellen,

In order to use the strategy of archiving all AIPs versions on MEEMOO, a field called "aip_version" was added to the sidecar, which will be used by RODA to find out if the updated AIP was successfully archived in MEEMOO, but to do that, this field needs to be searchable via the MEEMOO API. Could you please check with the MEEMOO team if it is possible to make this field searchable? The field name can be changed to whatever you consider most suitable.

Best regards, Gabriel

Hi Gabriel,

I checked and apparently there's a problem. To make a new field searchable as you ask would require modifications of the meemoo metadata profile for which we would need to ask a (payed) intervention by the system vendor. It would be more preferable to find a solution in RODA itself to link and manage the different versions of an AIP or is that not the problem you are facing here? I suppose they would all have unique ID's (Scala UUID's) but identical titles etc. In the meemoo perspective I suppose that these updated AIP's can simply be considered as new AIP's that make already existing ones obsolete?

Yours, Ellen

WimLo commented 3 years ago

In addition:

How does RODA actually know which version on meemoo to restore an AIP from?

A good alternative might be to add a field in the meemoo-sidecar and to store meemoo's pid in it.

I noticed that meemoo's pid of the AIP is not being stored in the version on RODA. It would be good to have it in the meemoo.xml metadata.

image

Wim

JelleKleevensVAI commented 3 years ago

Versioning to be added as part of iteration 2.

@Ellen why is the version field not showing in MAM? Does KEEPS have to do something or is it a meemoo issue?