EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #08606
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] custom JSON export
- To: "'David R Newman'" <drn@ecs.soton.ac.uk>, <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] custom JSON export
- From: <phil@buildvoc.co.uk>
- Date: Tue, 11 May 2021 18:21:42 +0100
CAUTION: This e-mail originated outside the University of Southampton.
David many thanks for the detail tutorial. Looks good The releasetool needs to have “status” as part of the response ] }, "status": 200 } Any ideas ? Really appreciate your help will be publishing the releasetool image soon which is connected to eprints, annif, and jena fuseki (for keywords) if anyone wants to use this tool for evaluating automatic subject indexing keywords.. Best Regards, Phil Stacey building regulations guidance for fire safety From: David R Newman <drn@ecs.soton.ac.uk>
Hi Phil, So it sounds like you need to make just a small tweak to the existing JSON export plugin. What you want to do is copy the existing JSON export plugin to your archive: cp EPRINTS_PATH/perl_lib/EPrints/Plugin/Export/JSON.pm EPRINTS_PATH/archives/ARCHIVE_NAME/cfg/plugins/EPrints/Plugin/Export/ReleaseToolJSON.pm Then edit at the top of the file, replacing each occurence of Export::JSON with Export::ReleaseToolJSON and replacing Export::TextFile with Export::JSON. When you get down to the "new" sub remove all the $self->... lines except the one for "name" and update
this to "Release Tool JSON". Then remove all the other subs (functions) except "sub _epdata_to_json". In there you will need to make a small change, removing: $subdata->{$field->get_name} = $value; and replacing with: my $field_name = $field->get_name; Once you have done this. Run "epadmin test" to check everything is OK and the reload the webserver (e.g. apachectl graceful). If you now go to an item and look under its available export formats you should now see one labelled "Release Tool JSON". This
will be exactly the same export (as JSON) except wherever eprintid was used before id will be used instead. However, this will mean that where documents use to reference the eprint with "eprintid" they will now use "id", which may not be what you want. If
so, you may need to amend the if statement to take the depth into account: $field_name = "id" if $field_name eq "eprintid" && $depth == 1; Regards David Newman On 11/05/2021 06:13, Phil Stacey via Eprints-tech wrote:
|
- Follow-Ups:
- Re: [EP-tech] custom JSON export
- From: <phil@buildvoc.co.uk>
- Re: [EP-tech] custom JSON export
- References:
- [EP-tech] custom JSON export
- From: <phil@buildvoc.co.uk>
- Re: [EP-tech] custom JSON export
- From: <phil@buildvoc.co.uk>
- [EP-tech] custom JSON export
- Prev by Date: [EP-tech] Antwort: Re: Antwort: RE: Short question about SSI in dynamic CGI output
- Next by Date: [EP-tech] number of items displayed at department level
- Previous by thread: [EP-tech] EPrints/CRIS
- Next by thread: [EP-tech] DOI handling in orcid_support_advance
- Index(es):