[Koha-bugs] [Bug 17511] Change authority linking subfield from $9 to $0

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17511

--- Comment #25 from David Cook <dcook at prosentient.com.au> ---
(In reply to Johanna Räisä from comment #24)
> (In reply to David Cook from comment #23)
> > (In reply to Johanna Räisä from comment #21)
> > > Do you mean putting Koha's internal link to authority linking subfield?
> > > 
> > 
> > I'm not 100% sure what you mean, but I think so, yes.
> 
> I meant that the authid would be changed to URI and saved that instead of
> integer value.
> 

Sounds good to me. 

The only thing to keep in mind is that the $9 is currently indexed into the
Koha-Auth-Number:w index which does mean that it's normalized and tokenized.
This could cause problems if there is an unencoded space in the URI for
instance. 

It might be wise for us to start using a "p" register instead of a "w"
register, and to start doing "exact" searches when querying this index... 

At least if you're using Zebra. I don't know about Elasticsearch...

> > Yeah that sounds good to me. So you wouldn't be storing authority records in
> > Koha? 
> 
> No we won't. 
> 

Interesting! Very interesting!

> We are making a plugin which fetches the authority via SRU or REST API while
> writing it to the field. We have already a similar approach to get
> vocabularies
> https://github.com/KohaSuomi/Koha/commit/
> 9dec82f3c28b41946f8b301dd9200cc36e92cd35

Sounds interesting. I'd like to hear more as you progress.

When you say that the plugin fetches the authority, do you mean that it fetches
it, extracts the relevant data, inserts it into the Koha bibliographic record,
and then discards the authority record?

I think that's such a great idea.

-- 
You are receiving this mail because:
You are watching all bug changes.