EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #05342
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: [solved] Subject based Views exclude top level
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Re: [solved] Subject based Views exclude top level
- From: "Alan.Stiles" <alan.stiles@open.ac.uk>
- Date: Wed, 20 Jan 2016 09:55:09 +0000
Thanks to Adam for some off-list assistance, the solution to this was, rather than trying to work around my bodge to views generation,
to change the eprint_fields_automatic routine that was updating the (multiple) field over which the view was built, so that it also included the relevant parent entries for any child entries, and then put the Update::Views routine back to its original state. Cheers, Alan From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Adam Field The new job is going well, so far :) Thanks for asking. Can we talk specifics here. Why are you trying to do this, and what are the names of these nodes? From:
<eprints-tech-bounces@ecs.soton.ac.uk> on behalf of "Alan.Stiles" <alan.stiles@open.ac.uk> Hi Adam (Hope you’re settling in to the new location and role!), You are correct regarding the hierarchy. I’d like the user to start at a menu listing
* parent 1 ** child 1 ** child 2 * parent 2 ** child 3 ** child 4 And not mention (or ideally spend effort creating a subject view for) the grandparent. From:
eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Adam Field Hi Alan So, you have a hierarchy like this: * grandparent ** parent 1 *** child 1 *** child 2 ** parent 2 *** child 3 *** child 4 Is that right? When you choose to browse by this view, were would you like the user to start, if not at the grandparent level? I’ve accomplished things a little like this by linking directly to a page that’s not the top level in the hierarchy. However, if you’re linking to your /view/
page, then in may involve creating a view.html page with links inserted by hand. From:
<eprints-tech-bounces@ecs.soton.ac.uk> on behalf of "Alan.Stiles" <alan.stiles@open.ac.uk> Does anyone know if there is a configuration parameter to not include the top level subject in a view based on a field using that subject hierarchy, similar to
the “showtop => 0” parameter on the definition for a field using a subject ?
i.e. we have a 3 level hierarchy but the view only includes entries for levels 2 and 3 and not level 1. Cheers, Alan -- The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302). The
Open University is authorised and regulated by the Financial Conduct Authority.
|
- Prev by Date: [EP-tech] Re: eprints REST API
- Next by Date: [EP-tech] Re: Update ePrints 3.3.10 -> .15: table name changes surprise the system
- Previous by thread: [EP-tech] eprints REST API
- Next by thread: [EP-tech] FW: [OR] DEADLINE fast approaching: OR2016 Proposals due Feb 1
- Index(es):