Please allow any indicator in any field (was: Re: [pu jsonalchemy] Aggregation of several fields into now)

2014-03-28 Thread Ferran Jorba
Hello Esteban, [...] > Don’t worry Ferran, I was using the authors 100 vs 700 as an example, > but it is the same case for other fields where you want to do > aggregations like this one. About the indicators, don’t worry either > we take good care of them, if needed, you can make the distinction

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-28 Thread Esteban Gabancho
Hey guys! I think we can say that we have a solution here. The authors list by default (Invenio demo site) will not contain a None value. Although this could be configurable depending on the data model of each installation. This list of authors is “connected” to first author and additional aut

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-28 Thread Esteban Gabancho
Hi Sam! On 27 Mar 2014, at 20:06, Samuele Kaplun mailto:samuele.kap...@cern.ch>> wrote: Additionally, as Lars mentioned, isn't the first author concept already captured by taking the first author in the authors list? Bibfield preserve field ordering so it's not really necessary to enforce a d

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-27 Thread Wagner, Alexander
Hi! First of all Marc defines 100/700, so skipping this breaks compatibility which is not at all clever. Don't do that. -- Kind regards, Alexander Wagner Subject Specialist Central Library 52425 Juelich mail : a.wag...@fz-juelich.de phone: +49 2461 61-1586 Fax : +49 2461 61-6103 www.fz-juel

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-27 Thread Wagner, Alexander
Hi Tibor! Perfectly agree with using 700 in display if no 100 exists due to an error. Also, something like bibcheck should complain about the record. Note that in our websubmit we enforce proper 100/700. But of course from bibedit (only available to staff) one could break it. Note, however, th

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-27 Thread Samuele Kaplun
Additionally, as Lars mentioned, isn't the first author concept already captured by taking the first author in the authors list? Bibfield preserve field ordering so it's not really necessary to enforce a difference between first and the other until the moment when the data are imported/exported

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-27 Thread Tibor Simko
On Thu, 27 Mar 2014, Wagner, Alexander wrote: > In some areas of research author ordering can cause sort of religious > wars. And I may also add that depending on the area of research, the > question "I want all my papers, but only those where I am the first > author" is /very/ common. Up to the no

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-27 Thread Tibor Simko
On Thu, 27 Mar 2014, Esteban Gabancho wrote: > The problem, or the question, comes when I don’t have a _first_author` > in which case I’m not sure about the content of the authors` field, it > could be i) only the list of `_additional_authors` or ii) `None` > follow by the the list of `_additional_

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-27 Thread Wagner, Alexander
Hi Lars! Be careful with this general simplified notion. In some areas of research author ordering can cause sort of religious wars. And I may also add that depending on the area of research, the question "I want all my papers, but only those where I am the first author" is /very/ common. Up to

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-27 Thread Esteban Gabancho
Hi Jan! On 27 Mar 2014, at 16:02, Jan Åge Lavik wrote: > With the None approach, it fear it can get confusing when iterating over all > authors (or whatever other field) as one then get None into the mix. If one > really wants to get the first author, maybe calling "first_author" (where > "fir

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-27 Thread Lars Holm Nielsen
On 27.03.2014 15:38, Esteban Gabancho wrote: Hey guys! I have a question about the aggregation of several fields into one. Taking the example of the authors, lets say I have two fields `_first_author` and `_additional_authors` and I want to aggregate then into `authors`. The common case, and t

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-27 Thread Ferran Jorba
Hello Alexander, Esteban et al, Alexander Wagner wrote: > > On 27.03.2014 15:38, Esteban Gabancho wrote: > >> I think the second solution is the closest one to reality, the `None` >> express that the record doesn’t have a first author. And I also think >> that we could apply this solution for ot

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-27 Thread Alexander Wagner
On 27.03.2014 15:38, Esteban Gabancho wrote: Hi! I think the second solution is the closest one to reality, the `None` express that the record doesn’t have a first author. And I also think that we could apply this solution for other cases where we have this kind of situation (like with the `

Re: [pu jsonalchemy] Aggregation of several fields into now

2014-03-27 Thread Jan Åge Lavik
Hi Esteban! With the None approach, it fear it can get confusing when iterating over all authors (or whatever other field) as one then get None into the mix. If one really wants to get the first author, maybe calling "first_author" (where "first_author" is a direct lookup to "_first_author") is en