Re: [VuFind-Tech] slashes in record ids

[Demian K. <dem...@vi...>]

Actually, the trunk VuFind implementation has always called the Summon module with the ID as a parameter rather than part of the URL path; I think Graham's problems relate to his local customizations to more tightly integrate Summon with the standard VuFind search module.

- Demian
________________________________________
From: Walker, David [dw...@ca...]
Sent: Friday, November 18, 2011 9:22 AM
To: Demian Katz; Seaman, Graham; vuf...@li...
Subject: RE: slashes in record ids

We also had this problem -- we seem to be on a common course, Graham. :-)

I finally just decided not to include the Summon record ID in the path, and kicked it out to the query string, like this:

   /summon/record?id=FETCH-LOGICAL-p439-3049e37df8c88a92704b69fa449d20e694a448c5e820340edaf767a366bd96860

It's nice to have the shorter form with your Solr records, since usually the catalog ID is something simple, like:

  /solr/record/b3088815

But since many of the Summon IDs are long and kinda ugly anyway, it didn't seem worth it.

Not sure if that is easy to do in the current version of VUFind (it would be trivial in version 2 using Zend Framework), since you have to tell VUFind to generate the links like this as well.  But just thought I'd throw out this marginally useful response. :-)

--Dave
-----------------
David Walker
Library Web Services Manager
California State University

-----Original Message-----
From: Demian Katz [mailto:dem...@vi...]
Sent: Friday, November 18, 2011 3:33 AM
To: Seaman, Graham; vuf...@li...
Subject: Re: [VuFind-Tech] slashes in record ids

Does anything on this page help?

http://www.jampmark.com/web-scripting/5-solutions-to-url-encoded-slashes-problem-in-apache.html

- Demian
________________________________________
From: Seaman, Graham [Gra...@rh...]
Sent: Friday, November 18, 2011 6:09 AM
To: vuf...@li...
Subject: [VuFind-Tech] slashes in record ids

I'm having a problem with our record Ids, used in the path to /Record/[id]. These aren't the normal internal ids from Solr, but are the ids returned to us by Summon, which mostly come indirectly from the original supplier and so are very varied in format. A few of them contain slashes; an example I came across today is oup_primary_10.1093/hgs/dcr0301

In fact this is actually url-encoded so the '/' appears as %2F, but that makes no difference to Apache: the standard rewrite rules which break the path into module, id, action fail with this kind of id. I can create one-off rules each time I find a supplier with record ids like this; eg:

RewriteRule ^(Record)/(oup_primary_[^/]+/[^/]+)/(.+)$       index.php?module=$1&id=$2&action=$3

and this is what I've done so far. But it's always reactive - someone reports that records are failing and I go and try to track them down - and it could have bad effects if the format of that supplier's id changes. Anyone got any ideas of better ways of handling this in Apache, before I go off and start inserting code to convert slashes to (say) pipe symbols and back all over the place?

Thanks
Graham

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Vufind-tech mailing list
Vuf...@li...
https://lists.sourceforge.net/lists/listinfo/vufind-tech