Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can I mark a new representation as a 'preservation' representation while doing a unoconv conversion? #68

Open
WimLo opened this issue Oct 27, 2021 · 3 comments
Labels
question Further information is requested RODA

Comments

@WimLo
Copy link
Collaborator

WimLo commented Oct 27, 2021

All I can see is that I can change the representation's type.

image

@WimLo WimLo added question Further information is requested RODA labels Oct 27, 2021
@luis100
Copy link
Collaborator

luis100 commented Oct 27, 2021

You have no option to do it while doing the conversion, you would have to mark them as preservation after doing the conversion.

@WimLo
Copy link
Collaborator Author

WimLo commented Oct 27, 2021

Hi Luis,

Let's suppose a scenario where I want to migrate all docx in an original representation and make a new representation with all the derivative files. I want to mark these new representations as a 'preservation' representations.

How can we practically do this? Would this usually imply doing a search operation on the SOLR backend after converting? Or is it usually so that you create a workflow that creates that combines the actions?

More generally, would you recommend marking a representation as being 'preservation' or 'access'. Is this usually done?

@luis100
Copy link
Collaborator

luis100 commented Oct 27, 2021

We would usually create a workflow/plugin that would combine several actions (plugins) and changes in the metadata (e.g. setting representation state as 'preservation', but this is more usually done in archives with a more homogenic set of file formats and representation than in what is your use case.

The important part is that the 'Original' representation is well-marked, as you would not normally have 'access' representations and, therefore, any non-original representations, or alternative representation could only serve the purpose of preservation. Instead of 'access' representations, archives usually have DIPs, which are kept separately from AIPs.

In your case, what should be in the AIP and what should be in the DIP should be considered together with the question of what should be on meemoo (meemoo only has AIPs and not DIPs) and what should remain on RODA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested RODA
Projects
None yet
Development

No branches or pull requests

2 participants