Hi, today we'll demonstrate the full workflow of a METS ingestion, from preparing the METS package to depositing it in Rosetta.

First let's take a look at the content we're going to ingest, in this example it will be several image files,
which we wish to store in Rosetta as one IE with two REPs, the first REP being a preservation master,
and the second being a modified master.

Under this directory Europe_Images, our data has to be organized according to the METS structure.

we are now on the SIP level: 

There must be a folder called content.
And optionally a dc.xml file, with the SIP title.

Now let's look at the content folder
We are now on the IE level.

Here we have at least one ie.xml file, but we could have more if we wish to ingest several IEs under this SIP.
We also have the streams folder, which contains the actual media files we want to ingest.
Alternatively, the files could be placed in a different location, in which case the IE.xml file would specify the full path where they can be found.

Now let's look at our ie.xml file:

The file describes one IE, and is divided into several sections.

The ie-dmd section contains the IE's Descriptive Metadata (or DMD for short), such as title and description.
The ie-amd section contains the IE's Administrative Metadata (or AMD for short), such as Entity Type and Access Rights Policy.

Next we have the Representations' Administrative Metadata, in our case we have two REPS one Preservation Master and one Modified Master.

Then we optionally have the files' administrative metadata, such as label or fixity.
We could also have a section for the files' descriptive metadata.

Finally we have the File Section which puts it all together defining the hierarchy of the IE,
In our case the first rep contains two files, and the second contains one file.
It is here that the file name or location is specified.

The ie.xml file can also contain a Structmap section, used for the delivery of complex IEs.

So now we have our ie.xml ready, in the content folde, in our SIP Package.
The next step is to put it in a mount folder where Rosetta can access it.

So let's open our FTP client, and drop our SIP package on the mount folder. The mount path is known to Rosetta as we shall soon see.

We are now ready to deposit the SIP, but since this is our first deposit in Rosetta,  
we need to make a few configurations beforehand in the Rosetta Management Module.


First let's take a look at our METS Material Flow under Deposits > Material Flows.

The Rosetta METS Deposit is an out-of-the-box automated material flow.

Note that our content structure is METS which is necessary for our METS deposit.
And our submission format is Internal.NFS.
We can update this submission format to fit the specifics of our deposit workflow, as we are about to do.

So under Deposits > Submission Format, let's Update Internal.NFS.

Crucially, this is where you provide the path of your mount, where we just placed the SIP.

Now for the desposit itself. In this demo, we will make a manual deposit using the METS Material flow,
but normally the deposit is done automatically by a submission job that runs regularly and checks if there are new SIP folders under this mount.

So to make the manual Deposit, go to Home > Add Deposit Activity
In the Deposit Module click Add Deposit Activity.

Now select Rosetta METS Depost, which is the Material Flow we've just seen. Next.

Now let's select the folder of our deposit. Next.

And finally Submit Deposit.

To view our deposited material, let's go to the Submitted tab, grab our SIP ID.
And back at the Management module, under Submissions Search for the SIP ID.
Here's our SIP, let's show it in the Assessor Workbench, click Work On.
This is the IE of our SIP, let's see it's structure.
here indeed we can see our IE has two REPS, Preservation and Modified Masters.
And each REP has its assigned files.

And under View Object, we can see our pictures!