Sorry if this is a little "stream of consciousness", my response was
authored as I was researching the literature...
This isn't a new topic... You may find this to be of use to establish
a historical context:
http://dublincore.org/usage/meetings/2002/05/citdcsv.html
http://epub.mimas.ac.uk/DC/citdcsv.html
http://dublincore.org/documents/dcmi-dcsv/
However, while they formalize an encoding of the value of the
citation. They do not provide a means to identify "where" in the
"dcterms:isPartOf" the article is located as separate dc values and
maybe because of this the community runs off in two separate
directions 1.) encode it in a dc:bibliographicCitation or 2.) make
new qualifications.
Unfortunately, the citation ends up duplicating most of the fields in
the dc and thus turns into a nightmare to maintain. So I understand
what your hoping to attain. This is where I think dc falls down on
its face and the community starts customizing it or creating a
separate namespace to maintain that detail.
I poked around for a DCMI Application Profile for expressing Journal
Articles and I kept returning full circle to the DCMI Citations
Working group... more specifically, based on this article...
http://epub.mimas.ac.uk/papers/appsmacecdl2000_full.html
It seems there are recommended encoding schemes for the dc:identifier
that will capture the detail about volume, issue, etc (See "Example
8" in below)
http://dublincore.org/documents/dc-citation-guidelines/
and yes thats all OpenURL...
I think the OpenURL approach is also sane. I think if we did a little
more work, we could introduce a means to parse out the metadata
values into "objects" that could be handled for presentation and
editing in places like the Manakin UI or in any Crosswalks rendered
out in OAI or the Packaging framework...
Ying's approach below is a solution that uses the current metadata
table to accomplish things. I do like that as well because it can be
customized to support different citation formats and its clear that
the bibliographicCitation field is better left to the application to
generate rather than duplicating metadata over and over in the
database. I hope maybe in the future such an approach could be
extended to support parsing values based on dcmi encoding schemes,
for instance, on dc:identifier OpenURL encodings to parse out the
appropriate values for the generated citation rather than custom
metadata fields. If implemented properly this could lead to some
better authority control and validation of metadata field values in
the dspace dublin core metadata.
-Mark
On Feb 8, 2008, at 8:07 AM, yinjin wrote:
Hi Robin,
I got a similiar request from our client. Our solution maybe not a
good one,
but I'd like to share it with you.
I'll take journal article as an example. We have very similar matadata
fields and we define our own citation format. Instead of letting
the user
input the citation in one field, we ask for each individual field
and then
assembly them together later for citation display. We defined a
seperate
schema to hold the metadata fields (e.g. journal, number, volume
and pages)
that don't fit into DC definitions. I designed an XML to define the
citation
format for each document type. Here is an example for journal article:
---------------------------------------------------------
<!-- JOURNAL ARTICLE -->
<citation name="journal-article" >
<!-- Author -->
<field>
<dc-schema>dc</dc-schema>
<dc-element>contributor</dc-element>
<dc-qualifier>author</dc-qualifier>
<display-format
multiple-value-seperator=",">@[EMAIL PROTECTED]</display-format>
</field>
<!-- Year -->
<field>
<dc-schema>dc</dc-schema>
<dc-element>date</dc-element>
<dc-qualifier>issued</dc-qualifier>
<display-format> @[EMAIL PROTECTED]</display-format>
</field>
<!-- Title -->
<field>
<dc-schema>dc</dc-schema>
<dc-element>title</dc-element>
<dc-qualifier></dc-qualifier>
<display-format> "@field@"</display-format>
</field>
<!-- Journal -->
<field>
<dc-schema>dlc</dc-schema>
<dc-element>identifier</dc-element>
<dc-qualifier>citationjournal</dc-qualifier>
<display-format> @field@</display-format>
</field>
<!-- Volume -->
<field>
<dc-schema>dlc</dc-schema>
<dc-element>identifier</dc-element>
<dc-qualifier>citationvolume</dc-qualifier>
<display-format> @field@</display-format>
</field>
<!-- Number -->
<field>
<dc-schema>dlc</dc-schema>
<dc-element>identifier</dc-element>
<dc-qualifier>citationnumber</dc-qualifier>
<display-format>(@field@)</display-format>
</field>
<!-- Pages -->
<field>
<dc-schema>dlc</dc-schema>
<dc-element>identifier</dc-element>
<dc-qualifier>citationpages</dc-qualifier>
<display-format>:@field@</display-format>
</field>
<field>
<dc-schema></dc-schema>
<dc-element></dc-element>
<dc-qualifier></dc-qualifier>
<display-format>.</display-format>
</field>
</citation>
---------------------------------------------------------
I coded a CitationManager to load the XML and assembly the citation
into
"dc.identifier.citation" field with given format. Though we used
dc.identifier.citation to store generated citation, we did not save
it to
the database - it allows us to change the citation format whenever
we want
(and that's one of requests from our client). I have tested it on
XMLUI and
OAI interfaces, I assume it should work for JSPUI too. To have this
happen,
there are several other changes made on DSpace code.
I have been struggled on how this should be implemented and not
sure if it
is a good solution. If you come up with a better idea, please let
me know
too.
Best,
Ying
----- Original Message -----
From: "Robin Taylor" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, February 08, 2008 5:45 AM
Subject: [Dspace-tech] Dublin Core Citations
I have a question for all the librarians and metadata experts out
there,
with apologies in advance for my sketchy metadata knowledge.
One of our schools is providing us with files of citations to go
along
with
the items. These citations are in Bibtex format
Eg.
@Article{journals/aim/Sloman99,
title = "Review of Affective Computing",
author = "Aaron Sloman",
journal = "AI Magazine",
year = "1999",
number = "1",
volume = "20",
url = "http://dblp.uni-trier.de/db/journals/aim/
aim20.html#Sloman99",
pages = "127--133",
}
I need to translate this into Dublin Core. In the case of a journal
article
it appears that DC does easily allow for the description of the
journal,
as
opposed to the article. DC does allow for a
'bibliographicCitation' but it
is expected that it will be one field containing either a human
readable
citation eg
Schrader, Alvin. "Internet Censorship: Issues for Teacher-Librarian."
Teacher Librarian 26, no.5 (1999): 5 pp
Or a machine readable equivelant, perhaps in OpenURL format.
See http://dublincore.org/documents/dc-citation-guidelines/ for a
better
description.
So, if I want to translate and store 'journal = "AI Magazine"'
from the
Bibtex file I would have to form a 'bibliographicCitation' with
this as
part
of it. If I ever wanted to reuse the constituent parts of the
bibliographicCitation I would need to deconstruct it. I would
prefer to
store the discreet parts and present them as a styled citation
when it
suits
my purpose.
I have seen a number of DC schema utilising dc.citation.xxx, but
as far
as
I am aware this is not 'approved' Dublin Core (see
http://dublincore.org/documents/2008/01/14/dcmi-terms).
Any suggestions as to how I can avoid going down the
'bibliographicCitation'
route would be much appreciated.
Thanks, and apologies for cross-posting.
Robin.
---------------------------------------------------------------------
----
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
----------------------------------------------------------------------
---
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
