EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #10383
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
RE: [EP-tech]
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>, "Abid Fakhre Alam" <abidfakhrealam@gmail.com>
- Subject: RE: [EP-tech]
- From: Matty Kerwin <matthew.kerwin@qut.edu.au>
- Date: Mon, 29 Jun 2026 22:42:51 +0000
|
CAUTION: This e-mail originated outside the University of Southampton.
The QUT ePrints implementation uses an internal ‘id’ field on creators, editors, and supervisors which is managed by us, and takes the form of a canonical name. For example, my id
is always “Kerwin, Matty”, which encodes to
https://eprints.qut.edu.au/view/person/Kerwin,_Matty.html That way we can do things like “Khan, Maria” and “Khan,
Maria Hameed” as two different people, and they get two different pages. The details of exactly how it was set up are lost to history, but it’s basically just another field on the person-type objects, and custom view configurations. Our “person” view
combined creators_id and editors_id, and there’s a separate supervisors view that uses supervisors_id. Cheers --
From: eprints-tech-request@ecs.soton.ac.uk <eprints-tech-request@ecs.soton.ac.uk>
On Behalf Of David R Newman Hi Abid, Having one browse view page for the same name will happen. You can create a creators ID browse view instead. This will mean you get different URLs as the last part will be whatever value you are using for your creators ID in the eprint workflow (typically
email address). However the ID is exposed in the URL. Here is a similar example, although it is using a secondary "internal" ID: You might change it to something like: push @{ $c->{browse_views} }, (
{
id => "creators_id", allow_null => 0, hideempty => 1, menus => [ {
fields => [ "creators_id", "contributors_id", "editors_id" ], new_column_at => [1, 1], mode => "sections", open_first_section => 1, group_range_function => "EPrints::Update::Views::cluster_ranges_30", grouping_function => "EPrints::Update::Views::group_by_a_to_z", }, ], order => "-date/title", variations => [ "type", "date;truncate=4,reverse", "DEFAULT", ], }); If you don't want the ID to be in the URL I believe you can hash this but I cannot remember how to do this right now. Also, the page you get will only display the ID of the creator and not their actual name, which may or may not be encoded in their ID
(e.g. Joe Bloggs may have the email address
Joe.Bloggs@example.org). This is something we are trying to improve with the concept of entities in the upcoming 3.5. However, we have not yet got round to making browse views for things like creators using these entities, which would be able to separate out to creators with the
same name. Regards David Newman Regards David Newman On 29/06/2026 06:03, Abid Fakhre Alam wrote:
| ||||
- Follow-Ups:
- Re: [EP-tech]
- From: Abid Fakhre Alam <abidfakhrealam@gmail.com>
- Re: [EP-tech]
- References:
- [EP-tech]
- From: Abid Fakhre Alam <abidfakhrealam@gmail.com>
- Re:[EP-tech]
- From: David R Newman <drn@ecs.soton.ac.uk>
- [EP-tech]
- Prev by Date: Re:[EP-tech]
- Next by Date: Re: [EP-tech]
- Previous by thread: Re:[EP-tech]
- Next by thread: Re: [EP-tech]
- Index(es):

