| Summary: | https://mana-kb.koha-community.org/ should not return a 404 error | ||
|---|---|---|---|
| Product: | Project Infrastructure | Reporter: | Paul Poulain <paul.poulain> |
| Component: | Mana-kb (server) | Assignee: | Alex Arnaud <alex.arnaud> |
| Status: | CLOSED FIXED | QA Contact: | Martin Renvoize (ashimema) <martin.renvoize> |
| Severity: | minor | ||
| Priority: | P5 - low | CC: | alex.arnaud, jonathan.druart, m.de.rooy, martin.renvoize |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: |
19.11.00
|
|
| Circulation function: | |||
| Bug Depends on: | 17047 | ||
| Bug Blocks: | 23075 | ||
|
Description
Paul Poulain
2019-05-15 12:29:39 UTC
I'd suggest it return a nice welcome page briefly describing what Mana is personally. Merge request is here: https://git.biblibre.com/biblibre/koha-mana/pulls/1 I was envisaging more of a human friendly splash page.. probably with a pretty definition of the Mana word (from Maori) and then a very short description/summary of what the 'product' is intended to do... something for the human reader that see's the page URL in the koha config page and wants to learn a bit more about what they're signing up to. The machine readable json is certainly an improvement over a 404, but it's still not all that friendly to the person who is most likely to ever try navigating to the page. Hi Alex, not sure how to test this. But I think what it does is returning a JSON type of answer. What I'd expect hitting the page from the browser would be a one page HTML page, just explaining what it is and maybe giving a hint on how to use it (link to the manual?). I think having a non-404 could still be good until we have figured this out, but don't think I can test? Just collided with Martin. Martin, Katrin, https://mana-* is an API and, IMO, is intended to return machine readable format only. This could be useful if we want koha to be able to check if the url is a valid mana instance. May be what you are expecting could be done on the user interface part: https://ui.mana-* [Update] merge request is here: https://gitlab.com/koha-community/koha-mana/merge_requests/1 I've been won around.. though in many ways I wish we had the URL's the other way around.. Right now it's very hard to discover that mana-ui exists from an end user perspective. I would have liked, for example: mana-kb.koha-community.org api.mana-kb.koha-community.org That way the more cryptic, aimed at machines, portal is on the more cryptic URL vs the user facing one being the more user friendly URL. (In reply to Martin Renvoize from comment #8) > I've been won around.. though in many ways I wish we had the URL's the other > way around.. > > Right now it's very hard to discover that mana-ui exists from an end user > perspective. The end-user has no reason to know (and use) mana-ui: it's only for admin purposes, you have access to nothing unless you're logged-in (and have admin permissions). ui let you parse mana DB, delete invalid shared infos, check users, ... No patch but signed off? What are we doing here ? We were testing the new return of the mana server - just hti mana-kb.koha-community.org Also comment#2 for the merge request with the code change for the mana server. See also bug 23161 This all looks reasonable and sane to me at this point and I don't believe it leads to any breaking changes. Passing QA, please go ahead and merge it into the project at your convenience Alex. Merged into upstream project https://mana-kb.koha-community.org and https://mana-test.koha-community.org are up-to-date with the related patches |