Adding multilang fields - Revision history

Libjlrs: Add another note about return value

2024-02-08T14:00:54Z

Add another note about return value

← Older revision		Revision as of 14:00, 8 February 2024
Line 131:		Line 131:

	}		}
	return undef;		return undef; # This is important. Using just a 'return;' or no return statement may break your repository e.g. when an EPrint revision file tried to be created.
	},		},

Libjlrs: Add note about return value for 'get_value'

2024-02-08T14:00:01Z

Add note about return value for 'get_value'

← Older revision		Revision as of 14:00, 8 February 2024
Line 62:		Line 62:
	return $self->call_property( "get_value", $object);		return $self->call_property( "get_value", $object);
	}		}
	return undef;		return undef; # This is important. Using just a 'return;' or no return statement may break your repository e.g. when an EPrint revision file tried to be created.
	}		}

Drn@ecs.soton.ac.uk: Fixed some broken links

2022-01-28T11:48:32Z

Fixed some broken links

← Older revision		Revision as of 11:48, 28 January 2022
Line 4:		Line 4:

	== Multilang fields and EPrints ==		== Multilang fields and EPrints ==
	EPrints supports the '''multilang''' field type (see [[Multilang]] for more details) which allows a user to insert different content for different languages. There are a few limitations with '''multilang''' fields though:		EPrints supports the '''multilang''' field type (see [[API:EPrints/MetaField/Multilang]] for more details) which allows a user to insert different content for different languages. There are a few limitations with '''multilang''' fields though:

	* When its value is printed it is shown in all languages containing content.		* When its value is printed it is shown in all languages containing content.
Line 32:		Line 32:

	== Adding a new field type (VirtualWithValue)==		== Adding a new field type (VirtualWithValue)==
	In order to create a multiple-language field we have to create an appropriate field type. EPrints' '''MetaField''' (see [[MetaField]] article for details) is a perfect candidate for this, and we need to extend it and override its '''get_value''' and '''set_value''' functions for the field to work properly with the rest of EPrints API, as well as its '''get_property_defaults''' function to sort out warnings for default values. The following code could be a rough implementation of such a field:		In order to create a multiple-language field we have to create an appropriate field type. EPrints' '''MetaField''' (see [[API:EPrints/MetaField\|MetaField]] article for details) is a perfect candidate for this, and we need to extend it and override its '''get_value''' and '''set_value''' functions for the field to work properly with the rest of EPrints API, as well as its '''get_property_defaults''' function to sort out warnings for default values. The following code could be a rough implementation of such a field:

	<source lang="perl">package EPrints::MetaField::Virtualwithvalue;		<source lang="perl">package EPrints::MetaField::Virtualwithvalue;

Kgoetz: add category howto

2018-08-30T06:22:07Z

add category howto

← Older revision		Revision as of 06:22, 30 August 2018
Line 1:		Line 1:
			[[Category:Howto]]

	EPrints' builtin fields are not multilingual, in the sense that there is only one version of each field -indirectly this means one language support. This page explains how to add multilingual versions of existing fields in EPrints and how they can be integrated with its subsystems.		EPrints' builtin fields are not multilingual, in the sense that there is only one version of each field -indirectly this means one language support. This page explains how to add multilingual versions of existing fields in EPrints and how they can be integrated with its subsystems.

Mamalos@eng.auth.gr: /* Warning for already populated repositories */

2016-07-07T10:29:37Z

Warning for already populated repositories

← Older revision		Revision as of 10:29, 7 July 2016
Line 10:		Line 10:

	== Warning for already populated repositories ==		== Warning for already populated repositories ==
	Once you follow this article's procedure, '''existing titles and abstracts''' will not be copied into their multilingual counterparts and '''access to them via the API will be lost'''!		Once you follow this article's procedure, '''existing titles and abstracts''' will not be copied into their multilingual counterparts and '''access to them via the API will be lost'''! The users of this plugin are requested to use EPrints API to copy the values from the old fields to the new ones. A script that copies the '''title''' value of each eprint to '''ml_title''' field's '''en''' and '''el''' languages can be found here:[https://github.com/mamalos/eprints/blob/master/help_scripts/set_ml_title.pl]. Please, use this script at your own risk and don't forget to change its content to reflect the languages of your repository. The same script can be used for copying the '''abstract''' field's values to '''ml_abstract''' '''en''' and '''el''' by replacing title with abstract in this script.

	== How to add a custom, multilingual field ==		== How to add a custom, multilingual field ==

Mamalos@eng.auth.gr: /* Adding search support for the ml_title field */

2016-06-07T12:27:10Z