- Koha-devel - lists.koha-community.org

Re: [Koha-devel] Koha-devel Digest, Vol 163, Issue 3
by Basu Talikoti 10 Jun '19

10 Jun '19

Hi You can configure indexing as follows this link https://wiki.koha-community.org/wiki/ICU_chains_configuration On Mon, Jun 10, 2019, 07:56 <koha-devel-request(a)lists.koha-community.org> wrote: > Send Koha-devel mailing list submissions to > koha-devel(a)lists.koha-community.org > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > or, via email, send a message with subject or body 'help' to > koha-devel-request(a)lists.koha-community.org > > You can reach the person managing the list at > koha-devel-owner(a)lists.koha-community.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Koha-devel digest..." > > > Today's Topics: > > 1. Arabic records indexing (MHE IT admin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 9 Jun 2019 00:04:54 +0300 > From: MHE IT admin <admin(a)mhe-krg.org> > To: Koha Devel <Koha-devel(a)lists.koha-community.org> > Subject: [Koha-devel] Arabic records indexing > Message-ID: > < > CA+O2VWVqPYkvcoE83QWJKRyfpra0qyjTukF_1+iFCvKVJcWZYA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > > We have finished entering all our library records to our Koha System > (18.05.05.000) and now we have an issue with indexing our Arabic records. > We can not search in Arabic to find records. > > Is there anyone out there who has done this and would like to share their > experience with us, please? > > http://library.koyauniversity.org > > Respectfully >

1 0

Koha 19.05.00 Released
by Nick Clemens 03 Jun '19

03 Jun '19

Hello everybody, It is with great pleasure that the Koha community announces the release of Koha 19.05, a major release of the Koha open source integrated library system. This release (as always) is the work of many librarians, developers, and community members who donate their time and effort to the project. Their contributions help shape the release, and the project going forward. None of this would be possible without them, and my sincere thanks goes out to everyone who had a hand in the project Extra thanks to all who helped me with this release, and with getting here to be the release manager for this version. I am so lucky to work with such a great team on a wonderful project and look forward to helping make Koha better on each release. Excelsior! Read the full release notes here: https://koha-community.org/koha-18-11-release/ Debian packages will be available shortly, if you are following a suite you will automatically upgrade to the next branch with this release, more info here: https://wiki.koha-community.org/wiki/Koha_on_Debian#Follow_a_suite:_stable.… Thank you all, Nick (kidclamp) -- Nick Clemens ByWater Solutions bywatersolutions.com Phone: (888) 900-8944 Pronouns: (he/him/his) Timezone: Eastern

7 6

Re: [Koha-devel] [Koha] Koha 18.05.13 release
by Tomas Cohen Arazi 31 May '19

31 May '19

Congrats for the great work! El vie., 31 may. 2019 a las 12:13, Lucas Gass (<lucas(a)bywatersolutions.com>) escribió: > The Koha community is proud to announce the release of Koha 18.05.13. > > Many thanks to all those who have supported the releases this cycle. > > The full release notes are available at: > https://koha-community.org/koha-18-05-13-release/ > > Debian packages will be uploaded in a few days. > > > Lucas > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Koha 18.11.06 release
by Renvoize, Martin 31 May '19

31 May '19

The Koha community is proud to announce the release of Koha 18.11.06. This is a maintenance release and is my last release as the 18.11.x series maintainer. The series is however in good hands going forward with Fridolin Somers taking it on for the next cycle. I'm sure he'll do a great job! Many thanks to all those who have supported the releases this cycle. The full release notes are available at https://koha-community.org/koha-18-11-06-release/ Debian packages will be uploaded in a few days. Best regards and thanks to all those who have contributed to this release. *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

2 1

Re: [Koha-devel] [Koha] Koha 19.05.00 Released
by Joy Nelson 31 May '19

31 May '19

Great work Nick!! On Thu, May 30, 2019 at 11:00 AM Lucas Gass <lucas(a)bywatersolutions.com> wrote: > Great job Nick!!! > > On Thu, May 30, 2019 at 9:53 AM Nick Clemens <nick(a)bywatersolutions.com> > wrote: > > > Hello everybody, > > > > It is with great pleasure that the Koha community announces the release > of > > Koha 19.05, a major release of the Koha open source integrated library > > system. > > > > This release (as always) is the work of many librarians, developers, and > > community members who donate their time and effort to the project. Their > > contributions help shape the release, and the project going forward. None > > of this would be possible without them, and my sincere thanks goes out to > > everyone who had a hand in the project > > > > Extra thanks to all who helped me with this release, and with getting > here > > to be the release manager for this version. I am so lucky to work with > such > > a great team on a wonderful project and look forward to helping make Koha > > better on each release. Excelsior! > > > > Read the full release notes here: > > https://koha-community.org/koha-18-11-release/ > > > > Debian packages will be available shortly, if you are following a suite > you > > will > > automatically upgrade to the next branch with this release, more info > here: > > > > > https://wiki.koha-community.org/wiki/Koha_on_Debian#Follow_a_suite:_stable.… > > > > Thank you all, > > Nick (kidclamp) > > > > -- > > Nick Clemens > > ByWater Solutions > > bywatersolutions.com > > Phone: (888) 900-8944 > > Pronouns: (he/him/his) > > Timezone: Eastern > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz > > https://lists.katipo.co.nz/mailman/listinfo/koha > > > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > -- Joy Nelson President, Koha Division ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

2 1

Koha Community Newsletter: May 2019
by kohanews 30 May '19

30 May '19

The Koha Community Newsletter for May 2019 is here: https://koha-community.org/koha-community-newsletter-may-2019/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Updates on koha-testing-docker
by Tomas Cohen Arazi 30 May '19

30 May '19

Hi all, I've made some changes on the koha-testing-docker project to make it even easier, following requests from community members: - A file defining cool aliases is included and an be used very easily [1]. Thanks Liz and Nick for their suggestions. - Now you can start koha-testing-docker without internet connection. You need to have the docker images up to date and downloaded of course. [1] https://gitlab.com/koha-community/koha-testing-docker#aliases [2] docker-compose pull -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Koha plugins on GitHub
by Fridolin SOMERS 27 May '19

27 May '19

Hi, It is actually not easy to find all existing plugins for Koha. Since a lot of them are on GitHub I propose the following guide lines : 1/ we name them koha-plugin-xxxx-yyyy 2/ we add the topic "koha-plugin", see https://github.com/topics/koha-plugin We also may use GitLab in the future. Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

2 1

Re: [Koha-devel] Restful API question
by Tomas Cohen Arazi 20 May '19

20 May '19

I misread your email while walking :-D You are right, the render call on the OpenAPI plugin requires you to feed it with a data structure that can be rendered as a JSON object. So what I'd loop on the results using fetch_hashref, and then do what is needed on each field (including mapping 1/0 into Mojo::JSON->true/Mojo::JSON->false if boolean, making integers really be integers, etc. El lun., 20 may. 2019 a las 11:40, Stephen Graham (<s.graham4(a)herts.ac.uk>) escribió: > Hi Tomas – the ability to extend the API with custom endpoints using the > plugin system is a great Koha feature! 😊 > > > > If I change my openapi.json to what you suggest I get: > > > > {"errors":[{"message":"Expected array - got > string.","path":"\/"}],"status":500} > > > > , so I guess I need to pass my data to the render method as an array and > not as a JSON string? If I do this I’m getting a can’t call method on > unblessed refence error: > > > > my @n = map { ( $_->encode_json ) } @{$notices}; > > return $c->render( status => 200, openapi => \@n ); > > > > I guess because @{$notices} is an array of hashes? I see in the Patrons.pm > REST module, that they are using a method called _*to*_api, which > according to the Perl doc: > > > > “Helper function that maps unblessed Koha::Patron objects into REST api > attribute names.” > > > > Sorry, it might be obvious, but do I need to iterate though my results and > convert them into…. I’m not sure what really. Looking at the _*to*_api > method it just seems to be mapping the database column names to the API > names, which I have done already in my initial sql query, and returns a > Patron object. Should I be able to do what I want with the data structure I > get from a fetchall_arrayref({})? > > > > Cheers, Stephen > > > > > > *From:* Tomas Cohen Arazi <tomascohen(a)gmail.com> > *Sent:* 20 May 2019 14:25 > *To:* Stephen Graham <s.graham4(a)herts.ac.uk> > *Cc:* koha-devel <koha-devel(a)lists.koha-community.org> > *Subject:* Re: [Koha-devel] Restful API question > > > > I think it should read like: > > "200": { > "description": "A list pending notifications", > "schema": { > "type": "array", > "items": { > "type": "object", > "properties": { > "userid": { > "type": "string", > "description": "Unique User ID" > }, > ... > } > } > } > } > > You can of course under-specify it, just saying you return JSON or the way > you did it, just avoiding OpenAPI altogether, but you loose the ability for > consumers to have a well documented API, and also you loose data validation > (in and out), which is very important when implementing the API. > > > > Happy to see others playing with this! Let me know how can I help1 > > > > El lun., 20 may. 2019 a las 10:05, Stephen Graham (<s.graham4(a)herts.ac.uk>) > escribió: > > > > Hi Tomas – the below is what I have. When I do my sql select I’m doing: > > > > > > > > select b.userid as userid, > > > > mq.message_id as messageid, > > > > mq.subject as subject, > > > > mq.content as body > > > > > > > > ,so the field names should map to the item names in the openapi.json. > I’m just not sure what I should be passing to the render method, and how to > describe that in the openapi.json file. At the moment I’m passing a string > – it’s JSON – but just a string. Maybe that isn’t right? When I look to see > how the Patrons API does it, it works like: > > > > > > > > my @patrons = $patrons->as_list; > > > > @patrons = map { _to_api( $_->TO_JSON ) } @patrons; > > > > return $c->render( status => 200, openapi => \@patrons ); > > > > > > > > and then seems to say it’s an array of objects in their json files > (patron.json and patron.json). > > > > > > > > Here is my openapi.json file: > > > > > > > > { > > > > "/notifications": { > > > > "get": { > > > > "x-mojo-to": > "Uk::Ac::Herts::Notifications::NotificationController#getPendingNotices", > > > > "operationId": "PatronEmailNotice", > > > > "tags": ["notifications"], > > > > "produces": [ > > > > "application/json" > > > > ], > > > > "responses": { > > > > "200": { > > > > "description": "A list of pending notices", > > > > "schema": { > > > > "type": "array", > > > > "items": { > > > > "userid": { > > > > "type": "string", > > > > "description": "Unique User ID" > > > > }, > > > > "messageid": { > > > > "type": "string", > > > > "description": "Unique Notice ID" > > > > }, > > > > "subject": { > > > > "type": "string", > > > > "description": "Notice Subject" > > > > }, > > > > "body": { > > > > "type": "string", > > > > "description": "Notice Body" > > > > } > > > > } > > > > } > > > > }, > > > > "404": { > > > > "description": "An error occured", > > > > "schema": { > > > > "type": "object", > > > > "properties": { > > > > "error": { > > > > "description": "An explanation for the error", > > > > "type": "string" > > > > } > > > > } > > > > } > > > > } > > > > }, > > > > "x-koha-authorization": { > > > > "permissions": { > > > > "borrowers": "1" > > > > } > > > > } > > > > } > > > > } > > > > } > > > > > > > > From: Tomas Cohen Arazi <tomascohen(a)gmail.com> > > Sent: 20 May 2019 12:28 > > To: Stephen Graham <s.graham4(a)herts.ac.uk> > > Cc: koha-devel <koha-devel(a)lists.koha-community.org> > > Subject: Re: [Koha-devel] Restful API question > > > > > > > > The most probable problem is the OpenAPI spec is wrong, and then the > plugin API is skipped altogether. > > > > > > > > If possible, share the openapi.json file in your plugin > > > > > > > > El lun., 20 de mayo de 2019 08:18, Stephen Graham <s.graham4(a)herts.ac.uk> > escribió: > > > > Hi all – I know it’s Kohacon this week so a lot of people will be busy > there, but just in case ……… (also sorry for the length of the email!): > > > > > > > > I testing creating a custom API endpoint using the Koha plugin system. > I’ve been using the code in the Kitchen sink plugin as a template, and it > seems to be working well apart from my lack of Swagger/OpenAPI knowledge – > I think it’s this I struggling with. I have three files: > > > > > > > > koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications.pm > > > > > koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/NotificationController.pm > > > > > koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/openapi.json > > > > > > > > The work is done in NotificationController.pm where I have a DBI call to > get the following fields: > > > > > > > > Borrower.userid > > > > Message_queue.message_id > > > > Message_queue.subject > > > > Message_queue.content > > > > > > > > I fetch the data, and convert into JSON (encode_json is a method from > Mojo::JSON) like: > > > > > > > > my $data = $sth->fetchall_arrayref({}); # return both fieldnames and > values > > > > my $json = encode_json($data); > > > > > > > > if I then do (i.e. use text): > > > > > > > > return $c->render( status => 200, text => $json) > > > > > > > > it works fine. If I call > https://herttest-staff.koha-ptfs.co.uk/api/v1/contrib/UH/notifications I > get json like: > > > > > > > > [ { > > > > “body”: “blah blah”, > > > > “messageid”: “1234567”, > > > > “subject”: “Important…”, > > > > “userid”: 99999999” > > > > } { > > > > Etc etc > > > > }] > > > > > > > > So in Perl terms it’s an array of hashes. Which is what I want. However, > if I try and use the openapi way that all the current “official” Koha > endpoints use e.g. > > > > > > > > return $c->render( status => 200, openapi => { notices => $json } ); > > > > > > > > it just doesn’t work. I have tried to map the field names with the > appropriate types in openapi.json. I’ve tried object type with properties > e.g. > > > > > > > > "responses": { > > > > "200": { > > > > "description": "A list of pending notices", > > > > "schema": { > > > > "type": "object", > > > > "properties": { > > > > "userid": { > > > > "type": "string", > > > > "description": "Unique User ID" > > > > }, etc > > > > > > > > , and I’ve tried array type with items: > > > > > > > > "responses": { > > > > "200": { > > > > "description": "A list of pending notices", > > > > "schema": { > > > > "type": "array", > > > > "items": { > > > > "userid": { > > > > "type": "string", > > > > "description": "Unique User ID" > > > > }, etc > > > > > > > > But I get a page not found error. When I pass my $json variable to the > render method using openapi how do I get it to work? I’m happy to use the > text way, but I want to understand where I’m going wrong. Any ideas, hints, > tips would be most welcome! > > > > > > > > Cheers, Stephen > > > > > > > > -------------------------------------- > > > > Stephen Graham > > > > Library Technology Consultant > > > > Content and Collections Team > > > > Library and Computing Services > > > > University of Hertfordshire > > > > Tel: 01707 286111 > > > > Ext: 77751 > > > > Email: s.graham4(a)herts.ac.uk > > > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > -- > Tomás Cohen Arazi > Theke Solutions (http://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F > -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Re: [Koha-devel] Restful API question
by Tomas Cohen Arazi 20 May '19

20 May '19

The _to_api method is required in patrons endpoint, only because we don't want to expose exactly the same attribute names as the DB columns and some others are just generated. So you need to make the objects match your spec. El lun., 20 de mayo de 2019 11:40, Stephen Graham <s.graham4(a)herts.ac.uk> escribió: > Hi Tomas – the ability to extend the API with custom endpoints using the > plugin system is a great Koha feature! 😊 > > > > If I change my openapi.json to what you suggest I get: > > > > {"errors":[{"message":"Expected array - got > string.","path":"\/"}],"status":500} > > > > , so I guess I need to pass my data to the render method as an array and > not as a JSON string? If I do this I’m getting a can’t call method on > unblessed refence error: > > > > my @n = map { ( $_->encode_json ) } @{$notices}; > > return $c->render( status => 200, openapi => \@n ); > > > > I guess because @{$notices} is an array of hashes? I see in the Patrons.pm > REST module, that they are using a method called _*to*_api, which > according to the Perl doc: > > > > “Helper function that maps unblessed Koha::Patron objects into REST api > attribute names.” > > > > Sorry, it might be obvious, but do I need to iterate though my results and > convert them into…. I’m not sure what really. Looking at the _*to*_api > method it just seems to be mapping the database column names to the API > names, which I have done already in my initial sql query, and returns a > Patron object. Should I be able to do what I want with the data structure I > get from a fetchall_arrayref({})? > > > > Cheers, Stephen > > > > > > *From:* Tomas Cohen Arazi <tomascohen(a)gmail.com> > *Sent:* 20 May 2019 14:25 > *To:* Stephen Graham <s.graham4(a)herts.ac.uk> > *Cc:* koha-devel <koha-devel(a)lists.koha-community.org> > *Subject:* Re: [Koha-devel] Restful API question > > > > I think it should read like: > > "200": { > "description": "A list pending notifications", > "schema": { > "type": "array", > "items": { > "type": "object", > "properties": { > "userid": { > "type": "string", > "description": "Unique User ID" > }, > ... > } > } > } > } > > You can of course under-specify it, just saying you return JSON or the way > you did it, just avoiding OpenAPI altogether, but you loose the ability for > consumers to have a well documented API, and also you loose data validation > (in and out), which is very important when implementing the API. > > > > Happy to see others playing with this! Let me know how can I help1 > > > > El lun., 20 may. 2019 a las 10:05, Stephen Graham (<s.graham4(a)herts.ac.uk>) > escribió: > > > > Hi Tomas – the below is what I have. When I do my sql select I’m doing: > > > > > > > > select b.userid as userid, > > > > mq.message_id as messageid, > > > > mq.subject as subject, > > > > mq.content as body > > > > > > > > ,so the field names should map to the item names in the openapi.json. > I’m just not sure what I should be passing to the render method, and how to > describe that in the openapi.json file. At the moment I’m passing a string > – it’s JSON – but just a string. Maybe that isn’t right? When I look to see > how the Patrons API does it, it works like: > > > > > > > > my @patrons = $patrons->as_list; > > > > @patrons = map { _to_api( $_->TO_JSON ) } @patrons; > > > > return $c->render( status => 200, openapi => \@patrons ); > > > > > > > > and then seems to say it’s an array of objects in their json files > (patron.json and patron.json). > > > > > > > > Here is my openapi.json file: > > > > > > > > { > > > > "/notifications": { > > > > "get": { > > > > "x-mojo-to": > "Uk::Ac::Herts::Notifications::NotificationController#getPendingNotices", > > > > "operationId": "PatronEmailNotice", > > > > "tags": ["notifications"], > > > > "produces": [ > > > > "application/json" > > > > ], > > > > "responses": { > > > > "200": { > > > > "description": "A list of pending notices", > > > > "schema": { > > > > "type": "array", > > > > "items": { > > > > "userid": { > > > > "type": "string", > > > > "description": "Unique User ID" > > > > }, > > > > "messageid": { > > > > "type": "string", > > > > "description": "Unique Notice ID" > > > > }, > > > > "subject": { > > > > "type": "string", > > > > "description": "Notice Subject" > > > > }, > > > > "body": { > > > > "type": "string", > > > > "description": "Notice Body" > > > > } > > > > } > > > > } > > > > }, > > > > "404": { > > > > "description": "An error occured", > > > > "schema": { > > > > "type": "object", > > > > "properties": { > > > > "error": { > > > > "description": "An explanation for the error", > > > > "type": "string" > > > > } > > > > } > > > > } > > > > } > > > > }, > > > > "x-koha-authorization": { > > > > "permissions": { > > > > "borrowers": "1" > > > > } > > > > } > > > > } > > > > } > > > > } > > > > > > > > From: Tomas Cohen Arazi <tomascohen(a)gmail.com> > > Sent: 20 May 2019 12:28 > > To: Stephen Graham <s.graham4(a)herts.ac.uk> > > Cc: koha-devel <koha-devel(a)lists.koha-community.org> > > Subject: Re: [Koha-devel] Restful API question > > > > > > > > The most probable problem is the OpenAPI spec is wrong, and then the > plugin API is skipped altogether. > > > > > > > > If possible, share the openapi.json file in your plugin > > > > > > > > El lun., 20 de mayo de 2019 08:18, Stephen Graham <s.graham4(a)herts.ac.uk> > escribió: > > > > Hi all – I know it’s Kohacon this week so a lot of people will be busy > there, but just in case ……… (also sorry for the length of the email!): > > > > > > > > I testing creating a custom API endpoint using the Koha plugin system. > I’ve been using the code in the Kitchen sink plugin as a template, and it > seems to be working well apart from my lack of Swagger/OpenAPI knowledge – > I think it’s this I struggling with. I have three files: > > > > > > > > koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications.pm > > > > > koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/NotificationController.pm > > > > > koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/openapi.json > > > > > > > > The work is done in NotificationController.pm where I have a DBI call to > get the following fields: > > > > > > > > Borrower.userid > > > > Message_queue.message_id > > > > Message_queue.subject > > > > Message_queue.content > > > > > > > > I fetch the data, and convert into JSON (encode_json is a method from > Mojo::JSON) like: > > > > > > > > my $data = $sth->fetchall_arrayref({}); # return both fieldnames and > values > > > > my $json = encode_json($data); > > > > > > > > if I then do (i.e. use text): > > > > > > > > return $c->render( status => 200, text => $json) > > > > > > > > it works fine. If I call > https://herttest-staff.koha-ptfs.co.uk/api/v1/contrib/UH/notifications I > get json like: > > > > > > > > [ { > > > > “body”: “blah blah”, > > > > “messageid”: “1234567”, > > > > “subject”: “Important…”, > > > > “userid”: 99999999” > > > > } { > > > > Etc etc > > > > }] > > > > > > > > So in Perl terms it’s an array of hashes. Which is what I want. However, > if I try and use the openapi way that all the current “official” Koha > endpoints use e.g. > > > > > > > > return $c->render( status => 200, openapi => { notices => $json } ); > > > > > > > > it just doesn’t work. I have tried to map the field names with the > appropriate types in openapi.json. I’ve tried object type with properties > e.g. > > > > > > > > "responses": { > > > > "200": { > > > > "description": "A list of pending notices", > > > > "schema": { > > > > "type": "object", > > > > "properties": { > > > > "userid": { > > > > "type": "string", > > > > "description": "Unique User ID" > > > > }, etc > > > > > > > > , and I’ve tried array type with items: > > > > > > > > "responses": { > > > > "200": { > > > > "description": "A list of pending notices", > > > > "schema": { > > > > "type": "array", > > > > "items": { > > > > "userid": { > > > > "type": "string", > > > > "description": "Unique User ID" > > > > }, etc > > > > > > > > But I get a page not found error. When I pass my $json variable to the > render method using openapi how do I get it to work? I’m happy to use the > text way, but I want to understand where I’m going wrong. Any ideas, hints, > tips would be most welcome! > > > > > > > > Cheers, Stephen > > > > > > > > -------------------------------------- > > > > Stephen Graham > > > > Library Technology Consultant > > > > Content and Collections Team > > > > Library and Computing Services > > > > University of Hertfordshire > > > > Tel: 01707 286111 > > > > Ext: 77751 > > > > Email: s.graham4(a)herts.ac.uk > > > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > -- > Tomás Cohen Arazi > Theke Solutions (http://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F >

1 0