EPrints Technical Mailing List Archive
Message: #06834
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] Unknown entries in creator browse
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] Unknown entries in creator browse
- From: "Alan.Stiles" <alan.stiles@open.ac.uk>
- Date: Wed, 13 Sep 2017 07:55:49 +0000
Good memory – looks like I missed that email conversation first time around. I think we surmounted the problem by using a local grouping function on the person view, which built on the [creators_id, editors_id]
for internal users in the same way as your view. The grouping function excludes entries from the sections hash of arrays it returns, where it can’t find the creators_id (or editors_id) in the user table. Alan From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Matthew Kerwin Wow, this discussion was ringing a lot of bells for me. I've (finally) managed to dig up this old thread: http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/2014-December/003730.html If anyone's interested, I ended up hacking EPrints::Update::Views::fieldlist_sizes to let me specify my own top-level SELECT function for the view. Also, I recently did this:
https://github.com/eprints/eprints/commit/2f9d827397680279d0a59808f8559306d0be8bb3 ...which changes the way 'allow_null' interacts with 'multiple' fields. It may be
related, but that was more for making sure allow_null=>1 works, rather than =>0 . Cheers -- Matthew Kerwin |
- Prev by Date: Re: [EP-tech] Unknown entries in creator browse
- Next by Date: Re: [EP-tech] Unknown entries in creator browse
- Previous by thread: Re: [EP-tech] Unknown entries in creator browse
- Next by thread: Re: [EP-tech] Unknown entries in creator browse
- Index(es):