EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #10384

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech]

CAUTION: This e-mail originated outside the University of Southampton.

Hi all,

Following up on this thread — thank you for the guidance on using an internal ID field for disambiguating creators with the same name.

I've implemented a browse view based on our institution's internal jgucreators_id field (our equivalent of creators_id, since we use a custom compound field called jgucreators), following the approach in the wiki article on internal IDs. The view is now generating correctly and successfully separates authors who share the same name but have different email IDs, which resolves the original duplicate-attribution issue.

However, the browse page currently displays the raw email address for each entry (e.g. dborisa@jgu.edu.in) rather than the person's actual name https://pure.jgu.edu.in/view/creators_id/index.D.html .

Could you advise on the recommended way within EPrints to render a friendly name label for an ID-based browse view, instead of showing the raw email? Our setup doesn't maintain centralized user accounts with internal IDs the way some examples assume — the name and ID are both stored as subfields within the same jgucreators compound field on each eprint record.

here is the part of configuration block of both the file related to this

eprint_fields.pl

{
name => 'creators',
type => 'compound',
multiple => 1,
fields => [
{
sub_name => 'name',
type => 'name',
hide_honourific => 1,
hide_lineage => 1,
family_first => 1,
},
{
sub_name => 'id',
type => 'text',
input_cols => 20,
allow_null => 1,
}
],
input_boxes => 4,
},
{
        name => 'jgucreators',
        type => 'compound',
        multiple => 1,
        fields => [
                {
                        sub_name => 'name',
                        type => 'name',
                        hide_honourific => 1,
                        hide_lineage => 1,
                        family_first => 1,
                },
                {
                        sub_name => 'id',
                        type => 'text',
                        input_cols => 20,
                        allow_null => 1,
                },
                {
            sub_name => 'author_category',
            type => 'subject',
        top => 'authorcat', # Links to your existing 'authorcat' subject tree
        },



views.pl

 {
id => "creators",
allow_null => 0,
hideempty => 1,
menus => [
{
fields => [ "creators_name" ],
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",
"DEFAULT",
],
},

];




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",
  ],
});



Thanks again for your help so far.

Thanks and Best Regards,
Abid Fakhre Alam


On Tue, Jun 30, 2026 at 4:14 AM Matty Kerwin <matthew.kerwin@qut.edu.au> wrote:

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

-- 
Matty Kerwin (he/him)

Senior Software Engineer
Digital Experience Plafforms, SSE
Digital Business Solutions

QUT-Logo

Queensland University of Technology
Email: matthew.kerwin@qut.edu.au
KG-X222, Kelvin Grove Campus

 

 

From: eprints-tech-request@ecs.soton.ac.uk <eprints-tech-request@ecs.soton.ac.uk> On Behalf Of David R Newman
Sent: Monday, June 29, 2026 5:13 PM
To: Abid Fakhre Alam <abidfakhrealam@gmail.com>; eprints-tech@ecs.soton.ac.uk
Subject: Re:[EP-tech]

 

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:

https://wiki.eprints.org/w/Using_Internal_IDs_for_Staff_Browse_Views#Create_Browse_View_based_on_Internal_IDs

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:

CAUTION: This e-mail originated outside the University of Southampton.

Dear Team,

I would like to report an issue with the Creator View page in EPrints.

We have identified a case where two different authors have the same forename and surname, but they belong to different departments and are different individuals. However, EPrints is indexing publications from both authors under a single creator page.

For example:
https://pure.jgu.edu.in/view/creators/Subramanian=3AVidya=3A=3A.html

the last two article one is book review and one the last article are belong to the different individual

As a result, publications belonging to two separate authors are being displayed on the same profile page, which leads to incorrect author attribution and confusion.

Could you please advise whether there is a configuration or solution to distinguish authors with identical names, such as using departmental affiliation, author ID, ORCID, or another unique identifier to generate separate creator pages?

We would appreciate your guidance on how to resolve this issue.

Thank you for your assistance.

Best Regards,
Abid Fakhre Alam

  • References:
    • [EP-tech]
      • From: Abid Fakhre Alam <abidfakhrealam@gmail.com>
    • Re:[EP-tech]
      • From: David R Newman <drn@ecs.soton.ac.uk>
    • RE: [EP-tech]
      • From: Matty Kerwin <matthew.kerwin@qut.edu.au>