Place is populated/adjusted in the Item.update method. It is initially
calculated off the original ordering of the metadata values added to the
Item. So it is not database record ordering. DSpace doesn't support changing
this order in ItemEdit or Submission (beyond your changing the values around
in the Item Edit fields yourself).
The ordering in the edit ui is across element/qualifier/place for existing
fields.
Ordering in the Summary and Detail Views is grouped by
element/qualifier/place
http://www.testathon.net/jspui/handle/123456789/164?mode=full&submit_simple=Show+full+item+record
Ordering in OAI is grouped by element/qualifier/place.
http://www.testathon.net/oai/request?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:www.testathon.net:123456789/164
Mark
On Thu, Jan 14, 2010 at 10:08 AM, Thornton, Susan M. (LARC-B702)[RAYTHEON
TECHNICAL SERVICES COMPANY] <susan.m.thorn...@nasa.gov> wrote:
> Hi Mark,
>
> Yes, it is column “place” in table metadatavalue that controls the
> order of things like lists of authors, however I don’t know exactly
> where/when “place” is populated when new records are submitted to DSpace.
>
>
>
> On a related note, we have long wanted to change the display of
> contributor.* in the short Item listing. For example, here is how our short
> listings appear where there are several contributor.author and corresponding
> contributor.organization metadata values in the record:
>
>
>
> Author: Smith, John
>
> Stiller, Ben
>
> Tilson, Joe
>
>
>
> Author Affiliation: NASA Langley Research Center
>
> Kennedy Space Center
>
> Case Western Reserve Univ
>
>
>
>
>
> We would like ours to look like this:
>
>
>
> Author(s): Smith, John NASA Langley
> Research Center
>
> Stiller, Ben Kennedy
> Space Center
>
> Tilson, Joe Case
> Western Reserve Univ
>
>
>
> Has anyone else done something like this?
>
> Thanks,
>
> Sue Walker-Thornton
>
> NASA Langley Research Center
>
> 757-224-4074
>
> susan.m.thorn...@nasa.gov
>
>
> ------------------------------
>
> *From:* Mark Diggory [mailto:mdigg...@atmire.com]
> *Sent:* Wednesday, January 13, 2010 11:39 PM
> *To:* Gary Browne
> *Cc:* dspace-tech@lists.sourceforge.net
> *Subject:* Re: [Dspace-tech] Display order of authors doesn't match
> submission order
>
>
>
> Gary,
>
> On Wed, Jan 13, 2010 at 3:32 PM, Gary Browne <gary.bro...@sydney.edu.au>
> wrote:
>
> Hi all,
>
> I'm running dspace 1.5.2. After submitting an item, the author listing is
> not preserved in the same order as the submission order. Is there some
> configuration in dspace.cfg which applies to this? I note that there is the
> jira issue DS-153 but I'm not clear whether this applies to 1.5.2. If so,
> are there instructions somewhere about applying patches to DSpace? I found
> this:
>
> http://wiki.dspace.org/index.php/ApplyingPatches
>
> but it doesn't actually describe the technical process.
>
>
> Quick, dirty solution.
>
> Take the following patched version of the file
>
>
> http://dspace.svn.sourceforge.net/viewvc/dspace/branches/dspace-1_5_x/dspace-api/src/main/java/org/dspace/submit/step/DescribeStep.java?revision=3394&pathrev=3394
>
> and place it in one of three possible locations:
>
> If using the full source distribution, you can replace the contents of the
> class directly...
>
>
> [dspace-src]/dspace-api/src/main/java/org/dspace/submit/step/DescribeStep.java
>
>
> or if using either distribution you cna choose one of the two following
> locations:
>
> if using jspui
>
>
> [dspace-src]/dspace/modules/jspui/src/main/java/org/dspace/submit/step/DescribeStep.java
>
> or if using xmlui
>
>
> [dspace-src]/dspace/modules/xmlui/src/main/java/org/dspace/submit/step/DescribeStep.java
>
>
> The later two place the class only within the webapplication you are
> building. While the first option will put the class into all
> webapplications and the lib directory used for the commandline
> functionality.
>
> ...
>
>
>
> Furthermore, I am running another (unpatched) 1.5.2 instance of dspace
> which doesn't suffer from this problem - how can that be?
>
>
> Without reviewing the code, I recall the order of the authors is actually
> driven off the order of database records within the metadatavalue table in
> database. (someone correct me if I'm in error). Thus differences in
> behavior may actually be an artifact of the database behavior. Or perhaps
> your running the 1.5.x branch from svn which has this patch applied?
>
> Unfortunately, this is an area where flat old DC records and conversely
> DSpace do not have particularly strong support. I suspect that capturing
> the priority of authors could possibly best be held in textual form within
> an additional field such as dc.identifier.bibliographicCitation field as an
> unambiguous original citation for the resource.
>
> I was reading...
> http://www.mail-archive.com/dspace-tech@lists.sourceforge.net/msg05213.html
>
> Which might make things "look" ok in the UI, but I wonder if its of any
> benefit in other parts of DSpace like crosswalks or oai. Relying on the
> order of XML fields for semantic detail about which is the first, second,
> third,... author is going to be both impossible to validate and preserve
> across disparate technologies/systems...
>
> See the Dublin Core usage guide, section 3...
>
> http://dublincore.org/documents/usageguide/
>
> Each Dublin Core element is optional and repeatable, and there is no
> defined order of elements. The ordering of multiple occurrences of the same
> element (e.g., Creator) may have a significance intended by the provider,
> but ordering is not guaranteed to be preserved in every user environment.
> Ordering or sequencing may be syntax dependent; for instance, RDF/XML
> supports ordering, but HTML does not.
>
>
> Best attempt to preserve this ordering detail in some field such as I've
> recommended with dc.identifier.bibliographicCitation, even though the usage
> here is not going to get recorded perfectly by your users in all cases it
> will be obvious at least somewhere in the record.
>
> Best Regards,
> Mark
>
>
>
> Mark R. Diggory
> Head of U.S. Operations - @mire
>
> http://www.atmire.com - Institutional Repository Solutions
> http://www.togather.eu - Before getting together, get t...@ther
>
--
Mark R. Diggory
Head of U.S. Operations - @mire
http://www.atmire.com - Institutional Repository Solutions
http://www.togather.eu - Before getting together, get t...@ther
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
