Hello all, Some of the questions above have become clearer, namely the structMap (should define a collection and contained items). I have decided to import using type METS instead of AIP, for no particular reason. Regarding 2), I've decided to import the mets.xml as a bitstream of the item being ingested, as discussed here http://dspace-tech.narkive.com/zUOSREuC/mets-sip-profile-ingest Although I still don't know how DSpace handles the PREMIS metadata, this way it's guaranteed the mets.xml is ingested and it isn't lost.
Still, some help or confirmation regarding this topic would be much appreciated! Thank you, Pedro Amorim 2016-04-12 17:09 GMT+00:00 Pedro Amorim <[email protected]>: > Dear all, > > I'm new to the terms OAIS, METS, AIP, SIP and DIP and have been surfing on > documentation the past couple of days. I'm trying to import METS packages > into DSpace using the packager plugin as posted below: > > bin/dspace packager -e [email protected] -t METS -p 123456789/14 test.zip > > Where *test.zip* is a zip file containing 2 files: > *mets.xml *- XML file compliant with DSpace and following the > requirements as in > > https://wiki.duraspace.org/display/DSPACE/DSpaceMETSSIPProfile#DSpaceMETSSIPProfile-StructuralRequirements > *test.jpg* - the digital object referenced in *mets.xml*. > > After the import, all seems fine. The descriptive metadata in DC is there > and also the digital object. > However I have a couple of questions: > > 1) Should I be importing with type AIP or type METS? What's the difference > between the 2? I have tested both and they seem pretty much the same; > > 2) Where can I see within DSpace the PREMIS metadata that's contained in > *mets.xml*? Or isn't it visible? > > 3) After exporting a DIP with the command: > bin/dspace packager -d -e [email protected] -i 123456789/16284 -t METS > diptest.zip > > The *mets.xml* contained in diptest.zip looks nothing like the original > *mets.xml* imported before, almost as if it was never ingested in the > first place and *mets.xml* in diptest.zip looks like it was generated on > export. > Shouldn't it contain the same amd and dmd of the original? > > 4) Regarding structMap, what purpose does it fulfill? Should there be the > collection the item will be inserted in? If so, how? By passing the -p > argument the item is created on the designated collection and the structMap > is ignored, it seems. > > 5) And finally, a short view of the mets.xml file I'm using in case > there's something else wrong with it: > > <mets <attributes>> > <metsHdr CREATEDATE="2016-04-07T17:36:26" > LASTMODDATE="2016-04-07T17:36:26"> > <agent ROLE="CREATOR" TYPE="OTHER" OTHERTYPE="SOFTWARE"> > <name>creator name</name> > <note>note/note> > </agent> > <agent ROLE="CREATOR" TYPE="OTHER" OTHERTYPE="VENDOR"> > <name>Vendor</name> > </agent> > </metsHdr> > <dmdSec ID="DCMD_ELEC"> > <mdWrap MIMETYPE="text/xml" MDTYPE="DC" LABEL="Eletronic"> > <xmlData> > <dc:title>Newspaper-AUT</dc:title> > <dc:language>pt</dc:language> > <dc:date>2016-04-07</dc:date> > <dc:type>Text.Newspaper</dc:type> > <dc:format>text/xml</dc:format> > <dc:publisher>CCS Content Conversion Specialists GmbH</dc:publisher> > </xmlData> > </mdWrap> > </dmdSec> > <dmdSec ID="DCMD_PRINT"> > <mdWrap MIMETYPE="text/xml" MDTYPE="DC" LABEL="Printed"> > <xmlData> > <dc:title>Newspaper-AUT</dc:title> > <dc:language>pt</dc:language> > <dc:type>Text.Newspaper</dc:type> > <dc:format>text/xml</dc:format> > <dc:identifier>01</dc:identifier> > </xmlData> > </mdWrap> > </dmdSec> > <amdSec ID="IMGPARAM00001"> > <techMD ID="IMGPARAM00001TECHMD"> > <mdWrap MDTYPE="PREMIS" MDTYPEVERSION='MDTYPEVERSION="1.02"'> > <xmlData> > <premis:object xsi:type="premis:file"> > <premis:objectIdentifier> > <premis:objectIdentifierType>local</premis:objectIdentifierType> > > <premis:objectIdentifierValue>01_20160101_0001_1_8-G-R0300</premis:objectIdentifierValue> > </premis:objectIdentifier> > </premis:object> > <premis:objectCharacteristics> > <premis:compositionLevel>0</premis:compositionLevel> > <premis:fixity> > <premis:messageDigestAlgorithm>SHA-512</premis:messageDigestAlgorithm> > > <premis:messageDigest>8a76efdd8a328efcaa44531bf74be219300cf49cca1bc8c1bf849347176433bb279abc833d47201ca9d407a8a51fd00ef1db26f4ad407f2a75adb952831b62bf</premis:messageDigest> > <premis:messageDigestOriginator>CCS Content Conversion > Specialists</premis:messageDigestOriginator> > </premis:fixity> > <premis:size>29907581</premis:size> > <premis:format> > <premis:formatDesignation> > <premis:formatName>tiff</premis:formatName> > <premis:formatVersion>1.02</premis:formatVersion> > </premis:formatDesignation> > </premis:format> > <premis:significantProperties> > <mix:mix> > <mix:BasicImageParameters> > ... > </mix:File> > </mix:BasicImageParameters> > <mix:ImageCreation> > ... > </mix:ImageCreation> > <mix:ImagingPerformanceAssessment> > ... > </mix:ImagingPerformanceAssessment> > <mix:ChangeHistory> > ... > </mix:ChangeHistory> > </mix:mix> > </premis:significantProperties> > </premis:objectCharacteristics> > </xmlData> > </mdWrap> > </techMD> > </amdSec> > <fileSec> > <fileGrp ID="MASTERGRP" USE="ORIGINAL"> > <file ID="IMG00001" CREATED="2016-04-07T17:36:22" ADMID="IMGPARAM00001" > MIMETYPE="image/tiff" SEQ="1" CHECKSUM="854e4ff5f73964d6c240172a5e74826d" > CHECKSUMTYPE="MD5" SIZE="29907581"> > <FLocat LOCTYPE="URL" xlink:href="teste.jpg"/> > </file> > </fileGrp> > </fileSec> > <structMap LABEL="Physical Structure" TYPE="PHYSICAL"> > ... > </structMap> > </mets> > > Any help is appreciated. > > Thank you, > > Pedro Amorim > -- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
