In addition to the work in bug 8207 that enables auth_finder use, it would be very useful when creating authorities to have the auth_finder plugin automatically fill out the relationship information in $w (in MARC21).
Created attachment 10552 [details] [review] Bug 8332: Add relationships to auth_finder for authority links In addition to the work in bug 8207 that enables auth_finder use, it would be very useful when creating authorities to have the auth_finder plugin automatically fill out the relationship information in $w (in MARC21). To test (note that you must either apply the patch for bug 8207 or manually add a thesaurus to a 5xx linking field in one of the authority type frameworks): 1. Create a new authority record. 2. Go to the 5xx tab. 3. Click the authority control plugin ellipsis. 4. Do a search for an authority. 5. Select a relationship type. 6. Note that after you choose an authority, that the $w control field is automatically populated with the relationship type.
Created attachment 10724 [details] [review] Signed-off patch After applying patch for bug 8207, I had been able to follow the test plan step by step, and get the expected result.
Created attachment 11254 [details] [review] Bug 8332: Add relationships to auth_finder for authority links In addition to the work in bug 8207 that enables auth_finder use, it would be very useful when creating authorities to have the auth_finder plugin automatically fill out the relationship information in $w (in MARC21). To test (note that you must either apply the patch for bug 8207 or manually add a thesaurus to a 5xx linking field in one of the authority type frameworks): 1. Create a new authority record. 2. Go to the 5xx tab. 3. Click the authority control plugin ellipsis. 4. Do a search for an authority. 5. Select a relationship type. 6. Note that after you choose an authority, that the $w control field is automatically populated with the relationship type. Signed-off-by: Frédéric Demians <f.demians@tamil.fr> After applying patch for bug 8207, I had been able to follow the test plan step by step, and get the expected result. Signed-off-by: Jared Camins-Esakov <jcamins@cpbibliography.com> Rebased on master 1 August 2012
QA Comments: Your utilisation of PROCESS for the problem of option's selection is interesting. But apparently it is not possible to translate the option values that way. Marked as Failed QA
Created attachment 11700 [details] [review] Bug 8332 follow-up: make strings translatable I made a silly mistake on the original patch and made the options untranslatable. This follow-up restores their translatability.
Created attachment 11702 [details] [review] Bug 8332 follow-up: make strings translatable I made a silly mistake on the original patch and made the options untranslatable. This follow-up restores their translatability. Signed-off-by: Jonathan Druart <jonathan.druart@biblibre.com>
Last patch is very simply. It allows translation for the option's values. Marked as Passed QA.
* patch does not apply with git bz: Switched to a new branch 'new/bug_8332' Already on 'new/bug_8332' Bug 8332 - Add relationships to auth_finder for authority links Bug 8332: Add relationships to auth_finder for authority links Apply? [yn] y fatal: cannot convert from UTF-8UTF-8 to UTF-8 Patch left in /tmp/Bug-8332-Add-relationships-to-authfinder-for-autho-xKVGYt.patch I've modified the /tmp/....patch to remove the 2nd "UTF-8" line in the header. Patch pushed. I've tested under UNIMARC, and could not find anything broken.
The relationship dropdown appears where appropriate.