[EP-tech] Re: Change EPrint field type.

[Gilles Fournié]

Hi,

Did you manage to solve your indexing problem ?

I have the same problem with a keyword field. We want to be able to look 
for the whole value "RIZ PLUVIAL" for example; and not for RIZ and 
PLUVIAL belonging to two different keywords.

 From my understanding of the Wiki page 
(http://wiki.eprints.org/w/Category:EPrints_Metadata_Fields#Ordering.2C_Indexing_and_Searching) 
the answer was in using text_index. But, it seems that it doesn't work 
this way : with text_index=>0, the keywords are no more searchable...

 From the same Wiki page 
(http://wiki.eprints.org/w/Category:EPrints_Metadata_Fields#Internal-use_and_Deprecated_Field_Types) 
it is also advised not to use the "id" type which is flagged as 
deprecated...

So what is the best way to get a field indexed as a whole and not by words ?

Thanks for your advices,
Gilles


Le 09/12/2014 20:15, sf2 a écrit :
>
> Hola Brian,
>
> You should be able to change it directly to "id" and run epadmin 
> update_database_structure - it will be the no-op since "text" and "id" 
> have the same db field definition. (in fact if you look at the source 
> code, you'll see that "text" is a special case of "id").
>
> Also.. in doubt, back up your DB before making the change.
>
> Seb
>
> On 09.12.2014 19:03, Brian D. Gregg wrote:
>
>> All,
>>
>> We have an EPrint field that we intended to use to hold ORCIDs 
>> originally defined as ‘type’ => ‘text’ and we have done so and thus 
>> we have data in the fields already.
>>
>> The problem is that an advanced search for an ORCID ID will return 
>> more than just the exact ORCID ID due to the fuzzy matching imposed 
>> on a ‘text’ field.  I was advised to change this to ‘type’ => ‘id’ to 
>> force the advanced search to use exact matching.
>>
>> My question is how can I change this field to ‘type’ => ’id’ 
>> including any database changes if they are needed (we are using 
>> MySQL)?  Obviously we edit the eprint_fields.pl file and change the 
>> definition, but what if anything else needs to be done on the 
>> database backend to accommodate this change?
>>
>> Any help would be appreciated.
>>
>> Thanks in advance,
>>
>> Brian.
>>
>> *Brian D. Gregg*
>>
>> /Solutions Architect /|/Manager Systems Development/
>>
>> University of Pittsburgh | University Library System
>>
>> Address: 7500 Thomas Blvd.  Room 129 Pittsburgh, PA 15208 
>> <https://maps.google.com/maps?q=7500+Thomas+Blvd,+Pittsburgh,+PA&hl=en&sll=41.117935,-77.604698&sspn=7.662465,13.73291&oq=7500+Tho&t=h&hnear=7500+Thomas+Blvd,+Pittsburgh,+Pennsylvania+15208&z=17>
>>
>> Tel: (412) 648-3264 | Email: bdgregg at pitt.edu 
>> <mailto:bdgregg at pitt.edu> | Fax: (412) 648-3585
>>
>>
>> *** 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/
>
>
>
> *** 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/