item import issue

[Shawn Kiewel]

I’m attempting to import an item using the Simple Archive Format. The import tool correctly processes all metadata files and content files in the item directory, however it then gives the following error:

 

Processing handle file: handle

It appears there is no handle file -- generating one

java.sql.SQLException: bad_dublin_core schema=SCHEMA.ELEMENT.QUALIFIER. Metadata field does not exist!

 

Grepping dspace.cfg for possible entries like that revealed only the defaults for the embargo fields, which I have overridden in local.cfg as follows:

 

embargo.field.terms = local.embargo.terms

embargo.field.liftdate = local.embargo.liftdate

 

These fields are defined in config/registries/local-types.xml, and the MetadataImporter was run on that file. metadata_local.xml is being parsed correctly, according to the output.

 

I’m at a loss where else to look for an undefined SCHEMA.ELEMENT.QUALIFIER string.

 

Any suggestions would be most appreciated.

 

Shawn

[Terry Brady]

Are those fields in your schema and metadata registry?  Look at the admin control panel to verify that they have been defined.

--
All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/9318360E-E795-4209-B4F9-E9C883C1F5C1%40gmail.com.

--

Terry Brady

Applications Programmer Analyst

Georgetown University Library Information Technology

https://github.com/terrywbrady/info

425-298-5498 (Seattle, WA)

[Shawn Kiewel]

Yes they are.

[Mark H. Wood]

I don't have an answer, but I find that the exception is only thrown
in two places: in org.dspace.content.DSpaceObjectServiceImpl:

./content/DSpaceObjectServiceImpl.java:211: throw new SQLException("bad_dublin_core schema=" + schema + "." + element + "." + qualifier + ". Metadata field does not exist!");
./content/DSpaceObjectServiceImpl.java:223: throw new SQLException("bad_dublin_core schema=" + schema + "." + element + "." + qualifier + ". Metadata field does not exist!");

So the literal "SCHEMA", "ELEMENT", "QUALIFIER" are being passed in
from somewhere. I wonder if there is something in local.cfg which is
interfering with the parsing of the overriding definition, possibly
causing parsing to halt before reaching it, or perhaps a problem with
quotation.

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

[Terry Brady]

Shawn,

Does your ingest folder contain a metadata_local.xml file as well as dublin_core.xml file?

For items that are not in the dc namespace, a separate metadata file should be provided.

Terry

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/9535C865-0378-46EF-BAE3-C2F4140C8F0F%40gmail.com.

[Shawn Kiewel]

Yes, and it is being processed properly according to the output. See this gist which is the full output:https://gist.github.com/smkiewel/af6b3eaa8f701d4b2a5ae0c865ed82bc

[Terry Brady]

Check this config setting.

https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/dspace.cfg#L692

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/F0EAB8A0-CBEF-4123-AEAF-4BFDE0E315F6%40gmail.com.

--

Sent from Gmail Mobile

[Shawn Kiewel]

Yes, I saw that string in dspace.cfg too, but I’m overriding that value in local.cfg:

 

embargo.field.terms = local.embargo.terms

embargo.field.liftdate = local.embargo.liftdate

 

 

Oh wait – I think I just saw it. It’s embargo.field.lift, not embargo.field.liftdate. Let’s see if that works.

 

Shawn

[Shawn Kiewel]

Yep, changing local.cfg to embargo.field.lift fixed it. Sorry for the fuss.

 

 

 

 

From: Shawn Kiewel <smki...@gmail.com>
Date: Thursday, September 19, 2019 at 12:36 PM
To: DSpace Technical Support <dspac...@googlegroups.com>
Subject: Re: [dspace-tech] item import issue

 

Yes, I saw that string in dspace.cfg too, but I’m overriding that value in local.cfg:

 

embargo.field.terms = local.embargo.terms

embargo.field.liftdate = local.embargo.liftdate

 

 

Oh wait – I think I just saw it. It’s embargo.field.lift, not embargo.field.liftdate. Let’s see if that works.

 

Shawn