Hi Agung PW,

You need to make sure you add this configuration before the end of the eprint_fields.pl file.  In particular before the last line which should just be:

];

If not it will not pick this up as a new field.  Also, I would expect there to be a syntax error, if you put this right at the end of the file.  If you have a lot of eprint records, this will take a long time to run.  However, I would expect some output at the end even if no fields are added.  This is what I saw when I ran epadmin of a test repository I knew needed no new fields needed adding:
 
0 datasets added
0 fields added
0 counters were added

If it had added a new field (assuming it is called 'course') I would have expected to see something like:

Added course to dataset eprint
0 datasets added
1 fields added
0 counters were added

Regards

David Newman

On 21/03/2023 8:55 am, Agung Prasetyo W. wrote:

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

Hi David,

I have tried to enter the field into eprints_field.pl, but when I run the epadmin update ArchiveID command, the process takes a very long time and no notification has appeared.

Regards,

Agung PW

On Tue, Mar 21, 2023 at 3:14 PM David R Newman via Eprints-tech <eprints-tech@ecs.soton.ac.uk> wrote:

Hi,

Subjects and Divisions boxes are subject type fields that include a part of the subject tree.  Therefore you would need to add a new sub-tree to your subject tree to include all your course options.  (You can use the Edit Subject page [1] linked from the Admin page to do this). Then you would need to add some configuration like the following to your archive's cfg/cfg.d/eprint_fields.pl file:

{
    name => 'course',
    type => 'subject',
    top => 'courses',
    browse_link => 'courses',
},

I have made some assumptions here:

1. That your would only ever need to store one course value against and eprint record.  If you need more you may need to add the line:

multiple => 1,

to the above configuration.

2. That the subject ID for the top of your courses sub-tree is 'courses'.

3. That you intend to create a browse view for courses like by default you will have for subjects and divisions.

Once you have added this configuration you will need to run the following command (substituting EPRINTS_PATH and ARCHIVE_ID) as appropriate:

EPRINTS_PATH/bin/epadmin update ARCHIVE_ID

Next you will need to add this field to your workflow. This will need a line like the following at the point you want this to appear in your workflow:

<component><field ref="course" /></component>

You may at this point also want to add some phrases.  You can does this via the Phrase Editor page link from the Admin page or edit a phrases file from the command line.  The minimum phrases you will need are eprint_fieldname_course and eprint_fieldhelp_course.

Once you have done all the is you will need to test the configuration is valid an reload the web server:

EPRINTS_PATH/bin/epadmin test
apachectl graceful

I have been working on improving the documentation pages about different types of metadata field as listed at https://wiki.eprints.org/w/Category:EPrints_Metadata_Fields.  I have not got to updating the subject field [2] yet but hope to do so today or later this week.  However, I hope to add some useful configuration examples to help when it comes to questions like yours here.

Regards

David Newman

[1] https://wiki.eprints.org/w/Admin/Config._Tools/Edit_subject
[2] https://wiki.eprints.org/w/Subject_field

On 20/03/2023 7:17 am, Agung Prasetyo W. via Eprints-tech wrote:

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

Hi,

I just added a field for a course with a lot of data. How can I make the view in the Details section so that it displays the course data like the divisions view or like Subject ?

Thank you.

Regards,

Agung Prasetyo WIbowo

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/