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.

Sign up for GitHub

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

Jump to bottom

Scope of search bar not always visible #39

Closed
pronguen opened this issue Jun 11, 2018 · 3 comments
Closed

Scope of search bar not always visible #39

pronguen opened this issue Jun 11, 2018 · 3 comments

Comments

@pronguen
Copy link
Contributor

The scope of the search bar is not always visible. For example when I edit a patron, the scope is not defined. See https://ils.test.rero.ch/editor/update/ptrn/13
@pronguen
Copy link
Contributor Author

The scope should always be displayed for a librarian, whatever it is.

The scope varies according to the page where the librarian is:

  • Menu "circulation" and related pages: scope "Documents"
  • Menu "documents" and related pages (editor, detailed view, item view, result list, ...): scope "Documents"
  • Menu "organisations" and related pages: scope "Libraries and locations" (for future, or members and locations for present)
  • Menu "users" and related pages: scope "Users"

@iGormilhit
Copy link

And the scope information should be more than just a placeholder.

@iGormilhit iGormilhit added this to the v.0.1.0a16 milestone Jun 28, 2018
@iGormilhit iGormilhit added UI and removed UI labels Oct 17, 2018
@iGormilhit iGormilhit removed this from the v.0.1.0a16 milestone Mar 25, 2019
@iGormilhit
Copy link

Not relevant anymore.

BadrAly pushed a commit that referenced this issue Apr 26, 2020
@jma @reropag
api: item availability (#41)
b2d5e07 
* Use item availability for the checkout.
* Check other loan states using Elasticsearch to compute item
  availability (closes #39)

Co-authored-by: Johnny Mariéthoz <[email protected]>
Co-authored-by: Gianni Pante <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iGormilhit @pronguen