search

inveniosoftware / invenio-records-rest

Invenio records REST API module.
https://invenio-records-rest.readthedocs.io
MIT License
4 stars 63 forks source link

docs: usage #170

Closed dinosk closed 6 years ago

dinosk commented 6 years ago

[ci skip] (Closes https://github.com/inveniosoftware/invenio-records-rest/issues/164, https://github.com/inveniosoftware/invenio-records-rest/issues/180)

Signed-off-by: Diego Rodriguez Rodriguez diego.rodriguez.rodriguez@cern.ch Co-Authored-By: Dinos Kousidis konstantinos.kousidis@cern.ch

diegodelemos commented 6 years ago

@lnielsen

regarding https://github.com/inveniosoftware/invenio-records-rest/issues/164#issuecomment-348212701

1.

Advanced customization Replace the search factory to do very advanced querying - i.e. exact control over what is sent to elasticsearch.

What would be an example of advanced querying? we are already using the elasticsearch library as it is with all the options.

2.

Tombstones and redirection error handlers

Regarding redirections, what should we show? Do we do the redirections with doctest as in https://github.com/inveniosoftware/invenio-records-rest/blob/574a221faca3ca6bb344b1fe8a0e14c67e85f541/tests/test_pid_resolver.py#L50-L61 and then show that the redirect error works? https://github.com/inveniosoftware/invenio-records-rest/blob/574a221faca3ca6bb344b1fe8a0e14c67e85f541/tests/test_pid_resolver.py#L80-L84

3.

Access control Principles

  • search filtering

Does this goes with the search factory?

lnielsen commented 6 years ago

Do you mind cleaning up the commit messages a bit, and at the same time rebase on latest master.