Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Allow IRN search without SPIRES- prefix #130

Closed
jrbl opened this Issue · 3 comments

2 participants

@jrbl
Collaborator

Originally on 2010-06-17

moved from https://savannah.cern.ch/task/index.php?13980

2010-02-16 20:18, original submission:

should be able to find records by SPIRES irn

these are stored in 970a (I believe) but need to strip leading "SPIRES-" to allow:

find irn 9170

to work

2010-06-03 22:03, comment #1:

Is it desirable to keep the SPIRES- on the IRN's stored in INSPIRE? If so, then the correct strategy appears to be:

- In search_engine_query_parser, translate irn keyword to 970a:
- prefix object portion with SPIRES- (if it's not there already)

If not, then the correct strategy appears to be:

- In search_engine_query_parser, translate irn keyword to 970a:
- Run a bit of SQL that strips the SPIRES- from what's in the database
- Stop the dumps from SPIRES from adding SPIRES- to the front of the IRNs.

2010-06-04 01:05, comment #2:

Tibor, please add my commit 3d4a178df from my Invenio branch '20100603.1700'. It should add this.

@jrbl jrbl self-assigned this
@jrbl
Collaborator

Originally on 2010-07-13

I've reintegrated this code on top of today's master, re-tested it, and pushed it out as branch trac-130. I've deleted the old branch for this code.

@jrbl
Collaborator

Originally on 2010-08-27

Also now available as 130-Websearch_IRNs_can_be_numbers_or_strings

@invenio-developers
Collaborator

Originally by Joe Blaylock jrbl@slac.stanford.edu on 2010-09-02

In [dd4bcbd]:

#CommitTicketReference repository="" revision="dd4bcbd3998fc21490440d328e1490993f901b00"
Websearch: IRNs can be numbers or strings

- SPIRES syntax parser now supports arguments of the form 'SPIRES-#####' or
  simply '########' for all of key, irn, record, and document, e.g.:
  'find irn 1000039', 'find record SPIRES-1000039', 'irn:SPIRES-1000039'
  are all equivalent.
  (fixes #130)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.