Yes, however I know there were some fiddles made within the database to include a “non-users” table which I think this particular change references. This has led to some issues updating things as bespoke functions and non-standard database tables have been wiped out. It’s complicated!

 

I will check the views.pl, though, and see if there’s anything I can salvage. I was hoping to tackle it from scratch though to avoid repeating past mistakes.

 

 

Sorry – slight mis-type on my part – I meant views.pl throughout.

 

You appear to have a working creators view on your live system : http://eprints.lincoln.ac.uk/view/creators/  which includes a view of possibly your stuff under the id 3762 ?

http://eprints.lincoln.ac.uk/view/creators/3762.html

 

Is this not what you are trying to do now?

Alan

 

 

 

Say all of the big words slowly so that thickie understands ;)

 

Okay, so I’ve added that to views.pl and it’s giving me the error when I try to view /person; I get that I’m probably not supposed to do that then? I tried creating view.pl in the /cfg.d folder but it results in a 404 presumably because it’s not generating the view?

 

 

Step 1 is can you successfully create and build  a view based on the creators_id field, so you get a view set which lists justs the ids (and counts of publications?) – this should be an addition to views.pl in [EPRINTS_ROOT]/archives/[ARCHIVE_ID]/cfg/cfg.d/ along the lines of this from the comments near the end of view.pl

        {

                id => "person",

                menus => [

                       {

                               fields => [ "creators_id","editors_id" ],

                               allow_null => 0,

                       }

               ],

                order => "-date/title",

                noindex => 1,

                nolink => 1,

               nocount => 0,

                include => 1,

        },

 

 

 

 

I get what this is trying to do and we’re certainly tagging with user ID. I’ve tried to implement the code as shown, both generating the view as “creators” and “people”, however I’m getting an error:

 

Can only perform process_distinctby on multiple fields with the same field type

 

I’m putting this largely down to this: https://cdn-images-1.medium.com/max/455/1*snTXFElFuQLSFDnvZKJ6IA.png

 

I really don’t fully know how to interpret the code in EPrints so anything like this is above me without a proper step by step explaining why specific things are being written in specific places and what they’re supposed to do.

 

Sorry if I seem inept!

 

 

My predecessor did something of that nature on our repository (see http://threader.ecs.soton.ac.uk/lists/eprints_tech/15598.html).

Essentially, you need to have tagged each creator (from your institution) on each publication record with their unique id, so the system can build a view based on the unique id, but when rendering the view, it uses their name (from the user record) rather than the id field.

Does that help, or still leave you with (more) questions?

Alan

 

 

Hello all!

 

So, I’m progressing with my migration – one of the things I want to do, which is something we get with our current repository, is to generate the creator browse based on a users ID number, rather than their name; so instead of eprints.lincoln.ac.uk/creator/john+smith or what have you, we get …/creator/1234. At present the name method is generating multiple pages for users who publish under different names, such as John Smith or J. Smith or John D. Smith. Also we may have different John Smith’s in our system and will want to identify them as such. So, the creator browse needs to be generated based on the user table.

 

Any ideas on how to go about doing this? The current method is not portable as the code will not work with the current version of EPrints, and I want to explore some non intrusive (plugin) ways of doing it rather than altering core functions.

 

Andrew

-- The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302). The Open University is authorised and regulated by the Financial Conduct Authority.