- Mar 30, 2012
-
- Mar 29, 2012
-
-
ssp authored
it is now a part of pazpar2-access
-
- Mar 28, 2012
- Mar 22, 2012
-
-
ssp authored
-
- Mar 21, 2012
- Mar 20, 2012
- Feb 24, 2012
-
-
ssp authored
Conflicts: Resources/Private/XSL/pz2-to-bibtex.xsl Resources/Private/XSL/pz2-to-ris.xsl Resources/Public/convert-pazpar2-record.php Resources/Public/pz2-neuerwerbungen.js
-
ssp authored
(the hack was temporarily needed to work around a pazpar2 bug)
-
ssp authored
-
ssp authored
in particular get rid of 'GOK' wherever possible as we now use generic CCL queries instead of GOK notations
-
ssp authored
-
ssp authored
-
ssp authored
We now firmly assume that we have CQL-style queries using ? as a wildcard and that our search terms are configured for optional truncated search (t=r) in pazpar2. The wildcard parameter in many queries is now used to replace an existing trailing ? with that parameter (e.g. *).
-
ssp authored
it didn’t match our DOM
-
ssp authored
-
ssp authored
seems to fit in better with the others in extension manage this way
-
ssp authored
the index was changed accordingly
-
ssp authored
-
ssp authored
and change the paths where necessary
-
ssp authored
-
ssp authored
in particular get rid of 'GOK' wherever possible as we now use generic CCL queries instead of GOK notations
-
ssp authored
-
ssp authored
-
ssp authored
We now firmly assume that we have CQL-style queries using ? as a wildcard and that our search terms are configured for optional truncated search (t=r) in pazpar2. The wildcard parameter in many queries is now used to replace an existing trailing ? with that parameter (e.g. *).
-
ssp authored
it didn’t match our DOM
- Jan 25, 2012
-
-
ssp authored
The script previously (and erroneously) depended on the server evaluating cookies and returning a correctly filled form (which is not the case in some situations with a caching proxy like Varnish that just serves the page without server contact). Rearrange things to first evaluate cookies and then trigger the search.
-
ssp authored
pazpar2 1.6.9 does not deal with these correctly: The nel index is set up as a phrase search (s=1) and we get a query conversion à la: pazpar2 -> SRU lkl=ia 5* -> pica.lkl="ia 5*" (lkl=ia 5*) -> pica.lkl="ia" and pica.lkl="5*" I.e. having () around the query parts breaks the query.
-
- Jan 18, 2012
-
-
ssp authored
The localisation worked in TYPO3 4.5, it seems that TYPO3 4.6 makes two silly assumptions: 1. the 'default' language is English 2. the 'default' language is the first language in locallang.xml which result in the English localisation not working if the first localisation in locallang.xml is German, as was the case here.
-
ssp authored
- Jan 16, 2012