Hi Ian,

Here is an example of what I was referring to. It uses dublin core, but
then adds some attributes that are more specific than the dublin core
correspondents, or are used by the machinery of the underlying repository.

* <dcterms:contributor oerdc:role="illustrator" oerdc:id="kef" oerdc:email="
k...@kef.com">Kathi Fletcher</dcterms:contributor> *
*
*
Here is the name space declaration.
*
*
*<oerdc:dc 
xmlns:oerdc=”http://oerpub.org/oerpub/oerdc<http://purl.org/oerpub/oer_dc>
”
         xmlns:dc="http://purl.org/dc/elements/1.1/";
         xmlns:dcterms="http://purl.org/dc/terms/";
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>*
*
*
I am not a schema expert, but just jumped in and also had some help from
folks with more experience. Maybe this will be useful for you.

Kathi

On Tue, Jul 17, 2012 at 7:48 AM, Wellaway, Ian <i.j.wella...@exeter.ac.uk>wrote:

>  Hi Kathi and Richard,****
>
> ** **
>
> Ignore my last email, I’ve figured it out by amending and adding to the
> list of simpledc terms in the swordv2-server.cfg file, which is what you
> said in your emails (the penny dropped after a while).****
>
> ** **
>
> Thank you both very much for your help.****
>
> ** **
>
> Best regards****
>
> ** **
>
> Ian****
>
> ** **
>
> ------------
>
> Ian Wellaway
>
> ****
>
> Senior System Support & Development Officer - Academic Systems (Room 911)
> Wednesdays only****
>
> &****
>
> Technical Developer, Open Exeter - Infrastructure Systems (Room 54) Monday
> - Tuesday, Thursday - Friday****
>
> ** **
>
> Exeter IT
> Laver Building
> University of Exeter
> EX4 4QE
> UK****
>
> ** **
>
> tel +44 1392 722852****
>
> ** **
>
> *From:* Wellaway, Ian
> *Sent:* 17 July 2012 09:49
> *To:* 'Kathi Fletcher'
> *Cc:* sword-app-tech@lists.sourceforge.net; Richard Jones
> *Subject:* RE: [sword-app-tech] Submitting metadata vis SWORD****
>
> ** **
>
> Thanks very much for your email Kathi,****
>
> ** **
>
> I’m not sure what ‘namespace an attribute on that that gives the added
> information/specialization that you need’ means or how to do it. Could
> you explain please?****
>
> ** **
>
> Best regards****
>
> ** **
>
> Ian****
>
> ** **
>
> ------------
>
> Ian Wellaway****
>
> Senior System Support & Development Officer - Academic Systems (Room 911)
> Wednesdays only****
>
> &****
>
> Technical Developer, Open Exeter - Infrastructure Systems (Room 54) Monday
> - Tuesday, Thursday - Friday****
>
> ** **
>
> Exeter IT
> Laver Building
> University of Exeter
> EX4 4QE
> UK****
>
> ** **
>
> tel +44 1392 722852****
>
> ** **
>
> *From:* kef....@gmail.com [mailto:kef....@gmail.com <kef....@gmail.com>] *On
> Behalf Of *Kathi Fletcher
> *Sent:* 13 July 2012 22:00
> *To:* Wellaway, Ian
> *Cc:* sword-app-tech@lists.sourceforge.net; Richard Jones
> *Subject:* Re: [sword-app-tech] Submitting metadata vis SWORD****
>
> ** **
>
> Ian,****
>
> ** **
>
> I think another alternative would be to use the dcterm that is closest and
> just namespace an attribute on that that gives the added
> information/specialization that you need.****
>
> ** **
>
> We did this for adding contributor specializations.****
>
> ** **
>
> Kathi****
>
> On Fri, Jul 13, 2012 at 1:30 PM, Richard Jones <rich...@cottagelabs.com>
> wrote:****
>
> Hi Ian,
>
> The qualifier approach that DSpace uses (dc.contributor.department for
> example) is an idiom based on the DCMI terms, so you can't strictly do
> it the way you suggest here, no, because what you've got isn't Dublin
> Core.  If you take a look at the DCMI spec
> (http://dublincore.org/documents/dcmi-terms/)  you will see that what
> DSpace represents as dc.title.alternative (for example), is actually
> correctly referenced as dcterms:alternative (which is a refinement of
> dcterms:title), and in SWORD we allow the DC XML to be embedded like
> <dcterms:alternative>subtitle</dcterms:alternative>, but only because
> that's a legitimate DCMI term.
>
> Your options are:
>
> 1/ Ignore all that and do it anyway!  Your example is legit XML, even
> if the namespace declaration is technically inaccurate, and if you
> update the ingester in DSpace to recognise your custom term (you might
> also need to update the disseminators to reflect it back over the
> sword API)
>
> 2/ Put your custom field in its own namespace.  Same comments about
> updating the ingesters as in (1) apply.
>
> Hope that helps.
>
> Cheers,
>
> Richard****
>
>
> On 13 July 2012 16:38, Wellaway, Ian <i.j.wella...@exeter.ac.uk> wrote:
> > Hi,
> >
> >
> >
> > In the python protocol for SWORD v2, is it possible to upload metadata
> that
> > has a qualifier as well as an identifier...Eg. dc.contributor.department.
> >
> >
> >
> > At present, I can upload metadata from the DCMI range but this only
> allows
> > as certain scope of data (such as contributor or title).
> >
> >
> >
> > Ideally, I’d like to write this as atom xml along the lines of:
> >
> >
> >
> > <?xml version='1.0'?>
> >
> > <ns0:entry xmlns:ns0='http://www.w3.org/2005/Atom'
> > xmlns:ns1='http://purl.org/dc/terms/'>
> >
> > <ns0:generator uri='http://bitbucket.org/beno/python-sword2'
> version='0.1'
> > />
> >
> > <ns0:updated>2012-07-09T17:06:44.696709</ns0:updated>
> >
> > <ns1:title>Test import 2</ns1:title>
> >
> >
> >
> > <ns1:contributor.department>Test text</ns1:contributor.department > ‘this
> > doesn’t work!
> >
> >
> >
> > </ns0:entry>
> >
> >
> >
> > Any ideas on this?
> >
> >
> >
> > Thanks
> >
> >
> >
> > Ian
> >
> >
> >
> > ------------
> >
> > Ian Wellaway
> >
> > Senior System Support & Development Officer - Academic Systems (Room 911)
> > Wednesdays only
> >
> > &
> >
> > Technical Developer, Open Exeter - Infrastructure Systems (Room 54)
> Monday -
> > Tuesday, Thursday - Friday
> >
> >
> >
> > Exeter IT
> > Laver Building
> > University of Exeter
> > EX4 4QE
> > UK
> >
> >
> >
> > tel +44 1392 722852
> >
> >
> >
> >****
>
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > sword-app-tech mailing list
> > sword-app-tech@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/sword-app-tech
> >
>
>
>
> --
>
> Richard Jones,
>
> Founder, Cottage Labs
> t: @richard_d_jones, @cottagelabs
> w: http://cottagelabs.com
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> sword-app-tech mailing list
> sword-app-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sword-app-tech****
>
>
>
> ****
>
> ** **
>
> --
> Katherine Fletcher, kathi.fletc...@gmail.com****
>
> Twitter: kefletcher <http://www.twitter.com/kefletcher> Blog:
> kefletcher.blogspot.com****
>
> ** **
>
> ** **
>
> ** **
>



-- 
Katherine Fletcher, kathi.fletc...@gmail.com
<kathi.fletc...@gmail.com>
Twitter: kefletcher <http://www.twitter.com/kefletcher> Blog:
kefletcher.blogspot.com
<kathi.fletc...@gmail.com>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
sword-app-tech mailing list
sword-app-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sword-app-tech

Reply via email to