[Dspace-tech] Packager import problem - PackageValidationException: No METS Manifest found

[James Rutherford]

Hello all,

I'm having some trouble with importing content with the new packager
system (org.dspace.content.packager). On the wiki page[1], it claims
that a package for import can be a "manifest-type document by itself,
containing only metadata and references to content". However, when I try
to import such a file from disk, I receive the following error:

pomona ~ # /opt/pf-dspace/bin/dsrun org.dspace.app.packager.Packager -c
pomona/71 -e james.ru...@hp.com -t METS -w
/opt/pf-dspace/upload/metadata.51996.tmp
Destination collections:
Owning Collection: 2006-11-13 16:51:57
org.dspace.content.packager.PackageValidationException: No METS Manifest
found (filename=mets.xml). Package is unacceptable.
at
org.dspace.content.packager.AbstractMETSIngester.ingest(AbstractMETSIngester.java:250)
at org.dspace.app.packager.Packager.main(Packager.java:274)
org.dspace.content.packager.PackageValidationException: No METS Manifest
found (filename=mets.xml). Package is unacceptable.

Any ideas what I'm doing wrong? The document that I'm trying to import
from is just a METS document (generated by the DSpace disseminator)
containing Item metadata and a reference to the bitstream. I can provide
the document I'm trying to import if it would help, but I don't think
it's the content that's the problem.

cheers,

Jim

[1] http://wiki.dspace.org/index.php/PackagerPlugins_it

--
James Rutherford
Research Engineer
HP Labs, Bristol, UK
+44 117 312 7066
james.ru...@hp.com

[Larry Stone]

> I'm having some trouble with importing content with the new packager
> system (org.dspace.content.packager). On the wiki page[1], it claims
> that a package for import can be a "manifest-type document by itself,
> containing only metadata and references to content". However, when I try
> to import such a file from disk, I receive the following error:

Sorry, that's the conceptual discussion of packages -- it is _possible_ for
a package to consist only of a manifest document, and in fact the METS AIP
I'm working on has a mode like that, but the METS SIP that was
implemented in 1.4 can only ingest a ZIP file.

So, if you embed the manifest in a Zip with the name "mets.xml", it
ought to be acceptable, so long as it does not reference any content
bitstreams or external (wrt the manifest) metadata. Since you mention
"reference to a bitstream", that may be a problem, the METS SIP spec
demands that any local file be part of the package (i.e. Zip file).

There will be a spec for the DSpace METS SIP posted soon. Right now the
best way to see exactly what to submit is to use the METS SIP disseminator
to produce a package of a similar Item.

-- Larry

> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> DSpace-tech mailing list
> DSpac...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech