Hi,

> similar at the time were the AIRway project which was based in Japan (at
> Hokkaido University I believe), but which, if iirc, was also working with

AIRway project is now able to interpret some metadata schemas other
than Japanese "junii2" schema.

See the targets and their metadata sample.
http://drf.lib.hokudai.ac.jp/drf/index.php?AIRway%2Ftargets

However, there seem to remain dialects even inside each schema, so the
program of the AIRway server is a pile of hard-coding...




Regards,
Shigeki Sugita, AIRway project
http://airway.lib.hokudai.ac.jp/index_en.html

2010/9/17 Michael White <[log in to unmask]>:
> Hi Graham,
>
>
>
>> However, adding new elements and qualifiers to Dublin Core [namespaces]
>> really doesn't help the cause of interoperability.
>
>
>
> Just to say that, in theory, I agree with this statement 100%, however, the
> world is a much more practical place!
>
>
>
> When we were looking at separating this data into discrete elements (several
> years ago now), the only other folk that appeared to be doing something
> similar at the time were the AIRway project which was based in Japan (at
> Hokkaido University I believe), but which, if iirc, was also working with
> Cranfield (?) – they had proposed the qualified versions of the citation
> element, and were also using this for a practical service across a number of
> different repositories (so not just a theoretical, intellectual exercise) –
> we looked about for any other profiles that might have other recommendations
> in this area, but didn’t find any, so we decided to adopt these elements at
> that time.
>
>
>
> Anyone who knows me, knows that metadata profiles and interoperability is
> one of my “soap box” issues (and I frequently find myself apologising for
> banging on about it ;-) ) – I’m not a librarian, cataloguer or metadata
> expert per se, but a techie who believes in interoperability – I do find it
> amazing that there are so many different standards/specifications/profiles
> in this area – it almost seems like every organisation or service that might
> want to make use of metadata, or promote standards and interoperability, has
> come up with its own profile, and, in many cases, these profiles have
> conflicting recommendations!! (OK, climbs down from soap box ;-) ).
>
>
>
> Of course, there is the school of thought that says “it doesn’t matter what
> you do within your repository, as long as you cross walk the data to the
> required profile for the specific service that is asking for it”, a valid
> point of view (although I’m still not convinced) and I’ve had many
> discussions with folk about this over the years . . . . J
>
>
>
>> As this is publication related metadata, my preference would be to see it
>> using the PRISM namespace.
>
>
>
> I’ve just had a(n admittedly very brief) look at this specification (in
> “PRISM_dublin_core_namespaces_2.1.pdf”), but I couldn’t see any specific
> recommendations for elements to keep the citation components in? Could have
> just missed it though . . .
>
>
>
> Cheers,
>
>
>
> Mike
>
> Michael White
> eLearning Developer
> eLearning Liaison & Development (eLD)
> 3V3a, Cottrell
> University of Stirling
> Stirling SCOTLAND
> FK9 4LA
>
> Email: [log in to unmask]
> Tel: +44 (0) 1786 466877
> Fax: +44 (0) 1786 466880
>
> http://www.is.stir.ac.uk/aboutis/teams/aldt/eld.php
>
>
>
> From: Graham Triggs [mailto:[log in to unmask]]
> Sent: 17 September 2010 13:52
> To: Michael White
> Cc: [log in to unmask]
> Subject: Re: Metadata, enumeration & pagination
>
>
>
> Hi,
>
>
>
> Getting better, discrete metadata into repositories is an important point.
> However, adding new elements and qualifiers to Dublin Core [namespaces]
> really doesn't help the cause of interoperability.
>
>
>
> As this is publication related metadata, my preference would be to see it
> using the PRISM namespace.
>
>
>
> http://www.prismstandard.org
>
>
>
> G
>
>
>
> On 17 September 2010 11:50, Michael White <[log in to unmask]> wrote:
>
> Hi David,
>
> Just to say that, yes, we use these metadata elements in our repository here
> at the University of Stirling - the submitter enters the citation in a
> single field (dc.relation), and then we break this down into the component
> parts during workflow (we tried it the other way round as well I believe,
> but settled on this approach). If the submitter doesn't enter the full
> citation (and even if they do), our workflow staff look this information up
> in order to double check it or add it as required.
>
> https://dspace.stir.ac.uk/dspace/handle/1893/1720?mode=full&submit_simple=Show+full+item+record
>
> There were a number of reasons for doing this - one of them being the work
> being done in Japan a while back on linking Open URL resolvers and
> repositories which requires to have this data in separate fields - as they
> were doing this work, and therefore suggesting some metadata elements for
> holding this data, we decided, in the absence of any other metadata
> guidelines in this area at the time, to just follow what they had done as it
> seemed sensible.
>
> Hope that helps.
>
> Mike
>
> Michael White
> eLearning Developer
> eLearning Liaison & Development (eLD)
> 3V3a, Cottrell
> University of Stirling
> Stirling SCOTLAND
> FK9 4LA
> Email: [log in to unmask]
> Tel: +44 (0) 1786 466877
> Fax: +44 (0) 1786 466880
> http://www.is.stir.ac.uk/aboutis/teams/aldt/eld.php
>
> -----Original Message-----
> From: Repositories discussion list [mailto:[log in to unmask]]
> On Behalf Of David Palmer
> Sent: 17 September 2010 11:13
> To: [log in to unmask]
> Subject: Metadata, enumeration & pagination
>
> Japan's National Institute of Informatics (NII) has made guidelines for
> metadata usage in IRs; "junii2 Guidelines",
>        http://www.nii.ac.jp/irp/archive/system/pdf/junii2guide_ver1.0.pdf
>
> They give these tags,
> - dc.identifier.volume
> - dc.identifier.issue
> - dc.identifier.spage
> - dc.identifier.epage
>
> I can see several IRs in Japan using these codes.  An example,
>
> http://ir.lib.shizuoka.ac.jp/handle/10297/2183?mode=full&submit_simple=Show+
> full+item+record
>
> I assume they use (created?) these because Dublin Core is silent on the
> issue.  We have the same problem in Hong Kong.  What to do for tags to show
> enumeration & pagination?  Now it is hopelessly all jumbled into
> dc.identifier.citation.
>
> Do IRs outside Japan use these same tags?  If not, what tags are used to
> show enumeration & pagination?  Is this issue being addressed in DSpace 1.6
> or 1.7?  Will all of us solve this problem by ourselves individually and
> thus create tags, variously weird & wonderful?  Let a thousand flowers
> bloom?
>
> David Palmer
> Scholarly Communications Team Leader
> The University of Hong Kong Libraries
> Pokfulam Road
> Hong Kong
> tel. +852 2859 7004
> http://hub.hku.hk
>
>
> --
> The Sunday Times Scottish University of the Year 2009/2010
> The University of Stirling is a charity registered in Scotland,
>  number SC 011159.
>
>
>
> ________________________________
> The Sunday Times Scottish University of the Year 2009/2010
> The University of Stirling is a charity registered in Scotland, number SC
> 011159.
>



--
SUGITA Shigeki <[log in to unmask]>
Otaru University of Commerce Library, JAPAN