[CODE4LIB] Σχετ: [CODE4LIB] New perl module MARC::File::MiJ -- marc-in-json for

2013-09-25 Thread dasos ili
And my biggest question is how one with such a template could import the logic, the rules behind a format. For instance how you handle a query that according to the format says: if the date of publication is not stored in the i.e. --1 field, then get it from the --2 field... Thank you both for

Re: [CODE4LIB] Σχετ: [CODE4LIB] New perl module MARC::File::MiJ -- marc-in-json for

2013-09-25 Thread Marc Chantreux
On Wed, Sep 25, 2013 at 08:34:33AM +0100, dasos ili wrote: And my biggest question is how one with such a template could import the logic, the rules behind a format. For instance how you handle a query that according to the format says: if the date of publication is not stored in the i.e. --1

[CODE4LIB] Σχετ: [CODE4LIB] New perl module MARC::File::MiJ -- marc-in-json for

2013-09-24 Thread dasos ili
My initial problem though with the marc-in-json approach is the complexity of the JSON, i am looking to find a simpler model in order to also make my queries, in ES for example, simpler to implement. If anyone has any examples of how make use of this marc - in - json output in order to use ES,

Re: [CODE4LIB] Σχετ: [CODE4LIB] New perl module MARC::File::MiJ -- marc-in-json for

2013-09-24 Thread Ross Singer
I mean, I'm not arguing against using a better a model for ES, but querying marc-in-json doesn't seem that complicated to me: { query: { query_string: { query: fields.100.a:Shakespeare } } } I don't see how you'd do this in MIR. But I'm starting to have a hard time following