- 08 Jun, 2012 1 commit
-
-
ssp authored
-
- 31 May, 2012 1 commit
-
-
ssp authored
show the remaining ones in the extended display
-
- 30 May, 2012 1 commit
-
-
ssp authored
-
- 29 May, 2012 1 commit
-
-
ssp authored
* avoid the acronym, be more descriptive * pull in the same changes in the JS client
-
- 07 May, 2012 1 commit
-
-
ssp authored
-
- 03 May, 2012 2 commits
- 24 Apr, 2012 5 commits
- 17 Apr, 2012 1 commit
-
-
ssp authored
-
- 30 Mar, 2012 1 commit
-
-
ssp authored
-
- 29 Mar, 2012 1 commit
-
-
ssp authored
it is now a part of pazpar2-access
-
- 28 Mar, 2012 3 commits
- 22 Mar, 2012 1 commit
-
-
ssp authored
-
- 21 Mar, 2012 3 commits
- 20 Mar, 2012 2 commits
- 24 Feb, 2012 16 commits
-
-
ssp authored
-
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
-