EPrints Technical Mailing List Archive
Message: #06692
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] full_test_status field
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] full_test_status field
- From: "Alan.Stiles" <alan.stiles@open.ac.uk>
- Date: Mon, 10 Jul 2017 09:27:05 +0000
From memory (through the jet-lag) I modified our eprints a few years ago to return public If there was at least one open attachment on an item as we have many where we received a word document version which is
attached and restricted and hidden, from which we have created a PDF version which is then publicly available, so it made more sense to class an item as public where there was something accessible. Alan From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Rory McNicholl or... cgi/oai2 could be updated so that it could handle filters for searches on the document dataset https://github.com/eprints/eprints/blob/3.3/cgi/oai2#L778 menas that cgi/oai2 applies the filters in the config
to eprints only More flexible config options could mean that you can send it filters for documents eg { meta_fields => [
"security" ],
value => "public", }, From the result set once could build down theunique list of $doc->value("eprintid") and this would be the result set you were looking for for the Driver set. I'm not sure this has any particular advantages to John's method. Maybe having a method to define custom sets of eprints based on document metadata would be useful for other OAI-PMH use cases? Maybe it would be slower as it is searching a bigger dataset? Cheers, Rory Rory McNicholl Lead developer Digital Archives & Research Technologies University of London Computer Centre Senate House Malet Street London WC1E 7HU t: +44 (0)20 7863 1344 The University of London is an exempt charity in England and Wales. From:
eprints-tech-bounces@ecs.soton.ac.uk <eprints-tech-bounces@ecs.soton.ac.uk> on behalf of John Salter <J.Salter@leeds.ac.uk> Hi all, Something for discussion: By default, EPrints sets the eprint->full_text_status field to: 'none' - if there are no docs 'public' - if there are some docs, and all are 'public' 'restricted' - if there are some docs, and at least one is not public. The full_text_status value is used as a filter in the OAI-PMH Driver set: https://github.com/eprints/eprints/blob/392474eec1/lib/defaultcfg/cfg.d/oai.pl#L59-L63 which means for items that have multiple documents, of which one is restricted, the item will not be included in the Driver set. Should there be another option for the full_text_status defined - e.g. 'some_public' - to show that at least one document is public? Currently, from the full_text_status value of 'restricted', it's not possible to determine whether this means *all* documents are restricted, or whether just one is. I realise this can be addressed on a repository-by-repository basis by updating the conifg, but I think that making it work better in core EPrints would be best. Any thoughts? Cheers, John |
- References:
- [EP-tech] full_test_status field
- From: John Salter <J.Salter@leeds.ac.uk>
- Re: [EP-tech] full_test_status field
- From: Rory McNicholl <rory.mcnicholl@ulcc.ac.uk>
- [EP-tech] full_test_status field
- Prev by Date: Re: [EP-tech] Translation Spanish help me!!
- Next by Date: [EP-tech] Creating a test repository from production repository
- Previous by thread: Re: [EP-tech] full_test_status field
- Next by thread: [EP-tech] Running EPrints under HTTPS all the time
- Index(es):