EPrints Technical Mailing List Archive
Message: #04337
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: How to set a field to be multilang
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Re: How to set a field to be multilang
- From: Timothy Miles-Board <timothy.miles-board@ulcc.ac.uk>
- Date: Thu, 18 Jun 2015 22:30:43 +0000
{ name => 'title', type => 'multilang', multiple => 1, fields => [ { sub_name => "text", type => "longtext", input_rows => 3, make_single_value_orderkey => 'EPrints::Extras::english_title_orderkey' } ], input_add_boxes => 1, }, Tim Timothy Miles-Board Web & Repositories Development Specialist, University of London Computer Centre 020 7863 1342 | 07742 970 351 | timothy.miles-board@london.ac.uk | @drtjmb The University of London is an exempt charity in England and Wales ________________________________________ From: eprints-tech-bounces@ecs.soton.ac.uk <eprints-tech-bounces@ecs.soton.ac.uk> on behalf of George Mamalakis <mamalos@eng.auth.gr> Sent: 18 June 2015 4:31 PM To: eprints-tech@ecs.soton.ac.uk Subject: [EP-tech] How to set a field to be multilang Hello again, I am trying to make my EPrints installation support multilanguage fields (eg. title, abstract, etc.). The thing I did that worked (which doesn't feel right to me, though) was adding a new Metadata field (eg. title_en) and add it to the database and workflow. On the documentation, on the other hand, I saw that there is a Multilang field type (./perl_lib/EPrints/MetaField/Multilang.pm) which should be used for this purpose. The strange thing is that its perldoc DESCRIPTION section starts with "not done", probably meaning that it's not implemented? Disregarding the last comment, when I changed ./archives/myarchive/cfg/cfg.d/eprint_fields.pl title field to read: { name => 'title', type => 'multilang', input_rows => 3, make_single_value_orderkey => 'EPrints::Extras::english_title_orderkey', }, and I reloaded epadmin, I got the following error: "Error in field property for eprint.title: fields on a multilang metafield can't be undefined" So, which is the proper way for adding multilanguage support in fields and display them in workflows? Thanks for all help in advance! -- George Mamalakis IT and Security Officer, Electrical and Computer Engineer (Aristotle Univ. of Thessaloniki), PhD (Aristotle Univ. of Thessaloniki), MSc (Imperial College of London) School of Electrical and Computer Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 *** 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/ *** EPrints developers Forum: http://forum.eprints.org/
- References:
- [EP-tech] OAI harvesting / records moving from live to buffer (or other non-deletion datasets).
- From: John Salter <J.Salter@leeds.ac.uk>
- [EP-tech] Re: OAI harvesting / records moving from live to buffer (or other non-deletion datasets).
- From: John Salter <J.Salter@leeds.ac.uk>
- [EP-tech] DSpace import plugin doesn't seem to parse UTF-8 correctly
- From: George Mamalakis <mamalos@eng.auth.gr>
- [EP-tech] Re: DSpace import plugin doesn't seem to parse UTF-8 correctly
- From: Timothy Miles-Board <timothy.miles-board@ulcc.ac.uk>
- [EP-tech] Re: DSpace import plugin doesn't seem to parse UTF-8 correctly
- From: George Mamalakis <mamalos@eng.auth.gr>
- [EP-tech] How to set a field to be multilang
- From: George Mamalakis <mamalos@eng.auth.gr>
- [EP-tech] OAI harvesting / records moving from live to buffer (or other non-deletion datasets).
- Prev by Date: [EP-tech] Re: DSpace import plugin doesn't seem to parse UTF-8 correctly
- Next by Date: [EP-tech] Re: Migrating from D-space (with files)
- Previous by thread: [EP-tech] How to set a field to be multilang
- Next by thread: [EP-tech] Re: How to set a field to be multilang
- Index(es):