Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

missing option "loose/strict" for searching by date #4

Open
wenamun opened this issue Jun 25, 2015 · 1 comment
Open

missing option "loose/strict" for searching by date #4

wenamun opened this issue Jun 25, 2015 · 1 comment

Comments

@wenamun
Copy link
Member

wenamun commented Jun 25, 2015

copy&paste from the papyri.info/search website (see also online help for option "extended" on the EDH search for some more examples):

Loose date ranges encompass all documents which may have been in existence within their span; strict ranges only those documents whose dates fall within both ends of the range. For instance, suppose there exists a document dated between 150 - 350 AD. If a user selects a loose range of 100 - 200 AD, this document will be returned, as it may indeed have been in existence during that period. If the user switches to a strict range, however, this document will be excluded, as its latest possible date falls outside the bounds of the search.

default/only option in the moment in the EAGLE search is "loose", so there needs to be an option to choose "strict".

@PietroLiuzzo
Copy link

currently the query simply asks : http://search.eagle.research-infrastructures.eu/solr/EMF-index-cleaned/select?q=entitytype:artifact AND (notbefore:[15 TO 20] OR notafter:[15 TO 20])

which si loose and probably not a very clever query.

for a "strict" option (to be added to the requirements?) perhaps http://search.eagle.research-infrastructures.eu/solr/EMF-index-cleaned/select?q=entitytype:artifact AND (notbefore:[15 TO 20] AND notafter:[15 TO 20])

but this eventually in my understanding of this, which is poor, would simply force the presence of both information (which are not always given) and therefore looks like just an apparent restriction.

what happens in a strict search to something which is only dated notBefore 180 without a notAfter ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants