Hi,
As promised earlier today during the call, I've released some very
simple code for indexing and displaying EAD XML. I wanted to get this
out there just so we'd have some other working EAD code to react to
and possibly collaborate to improve. So please let me know what you
think and/or fork it and send pull requests.
Answer yes to everything and start Solr before indexing EAD. (It uses
the Blacklight template from HEAD which allow extra head content.)
This code was just ripped out of our Historical State site [1] so lots
of NCSU specific code remains. Also, the intention in that application
was not to display everything possible in the EAD, but just to give a
the gist and refer the user to the full collection guide if they need
the full collection guide display [2]. Certainly more work could be
done to display more of the information.
-- You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
To post to this group, send email to blacklight-development@googlegroups.com.
To unsubscribe from this group, send email to blacklight-development+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/blacklight-development?hl=en.
Can you provide instructions for installing your code as a plugin to an existing app that already includes BL? Or is your code not yet factored to allow this?
Jason Ronallo wrote:
> Hi,
> As promised earlier today during the call, I've released some very
> simple code for indexing and displaying EAD XML. I wanted to get this
> out there just so we'd have some other working EAD code to react to
> and possibly collaborate to improve. So please let me know what you
> think and/or fork it and send pull requests.
> Answer yes to everything and start Solr before indexing EAD. (It uses
> the Blacklight template from HEAD which allow extra head content.)
> This code was just ripped out of our Historical State site [1] so lots
> of NCSU specific code remains. Also, the intention in that application
> was not to display everything possible in the EAD, but just to give a
> the gist and refer the user to the full collection guide if they need
> the full collection guide display [2]. Certainly more work could be
> done to display more of the information.
-- You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
To post to this group, send email to blacklight-development@googlegroups.com.
To unsubscribe from this group, send email to blacklight-development+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/blacklight-development?hl=en.
On Mon, May 3, 2010 at 5:35 PM, Jonathan Rochkind <rochk...@jhu.edu> wrote:
> Can you provide instructions for installing your code as a plugin to an
> existing app that already includes BL? Or is your code not yet factored to
> allow this?
> Jason Ronallo wrote:
>> Hi,
>> As promised earlier today during the call, I've released some very
>> simple code for indexing and displaying EAD XML. I wanted to get this
>> out there just so we'd have some other working EAD code to react to
>> and possibly collaborate to improve. So please let me know what you
>> think and/or fork it and send pull requests.
>> Answer yes to everything and start Solr before indexing EAD. (It uses
>> the Blacklight template from HEAD which allow extra head content.)
>> This code was just ripped out of our Historical State site [1] so lots
>> of NCSU specific code remains. Also, the intention in that application
>> was not to display everything possible in the EAD, but just to give a
>> the gist and refer the user to the full collection guide if they need
>> the full collection guide display [2]. Certainly more work could be
>> done to display more of the information.
> --
> You received this message because you are subscribed to the Google Groups
> "Blacklight Development" group.
> To post to this group, send email to
> blacklight-development@googlegroups.com.
> To unsubscribe from this group, send email to
> blacklight-development+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/blacklight-development?hl=en.
-- You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
To post to this group, send email to blacklight-development@googlegroups.com.
To unsubscribe from this group, send email to blacklight-development+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/blacklight-development?hl=en.
Thanks for this, Jason. I installed a new application and it worked
great. I was able to index the sample EAD and MARC data, as well as
some LC marc records, the ead xml documents that come with the
blacklight app itelf, and an ead doc that I exported from Archivist's
Toolkit.
I have a question about displaying the contents of the ead files. The
README states that it only handles numbered parts of the collection
inventory. I believe the ead docs that I indexed that were not part
of the data set that came with your plugin do not use numbered parts
for their inventory. So, those documents do not display their
inventory, just the scope and content info. Is it possible to change
that? Or should I look into redoing the ead output from AT, for
example, to use numbered parts in the inventory.
Please feel free to point me the way to documentation on EAD formats,
or other relevant info. I'm relatively new to EAD, but I'd be
interested to know the issues behind inventory display in your
blacklight plugin.
thanks!
...adam
On May 3, 5:33 pm, Jason Ronallo <jrona...@gmail.com> wrote:
> Hi,
> As promised earlier today during the call, I've released some very
> simple code for indexing and displaying EAD XML. I wanted to get this
> out there just so we'd have some other working EAD code to react to
> and possibly collaborate to improve. So please let me know what you
> think and/or fork it and send pull requests.
> Answer yes to everything and start Solr before indexing EAD. (It uses
> the Blacklight template from HEAD which allow extra head content.)
> This code was just ripped out of our Historical State site [1] so lots
> of NCSU specific code remains. Also, the intention in that application
> was not to display everything possible in the EAD, but just to give a
> the gist and refer the user to the full collection guide if they need
> the full collection guide display [2]. Certainly more work could be
> done to display more of the information.
> --
> You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
> To post to this group, send email to blacklight-development@googlegroups.com.
> To unsubscribe from this group, send email to blacklight-development+unsubscribe@googlegroups.com.
> For more options, visit this group athttp://groups.google.com/group/blacklight-development?hl=en.
-- You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
To post to this group, send email to blacklight-development@googlegroups.com.
To unsubscribe from this group, send email to blacklight-development+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/blacklight-development?hl=en.
> Thanks for this, Jason. I installed a new application and it worked
> great. I was able to index the sample EAD and MARC data, as well as
> some LC marc records, the ead xml documents that come with the
> blacklight app itelf, and an ead doc that I exported from Archivist's
> Toolkit.
> I have a question about displaying the contents of the ead files. The
> README states that it only handles numbered parts of the collection
> inventory. I believe the ead docs that I indexed that were not part
> of the data set that came with your plugin do not use numbered parts
> for their inventory. So, those documents do not display their
> inventory, just the scope and content info. Is it possible to change
> that? Or should I look into redoing the ead output from AT, for
> example, to use numbered parts in the inventory.
> Please feel free to point me the way to documentation on EAD formats,
> or other relevant info. I'm relatively new to EAD, but I'd be
> interested to know the issues behind inventory display in your
> blacklight plugin.
> thanks!
> ...adam
> On May 3, 5:33 pm, Jason Ronallo <jrona...@gmail.com> wrote:
> > Hi,
> > As promised earlier today during the call, I've released some very
> > simple code for indexing and displaying EAD XML. I wanted to get this
> > out there just so we'd have some other working EAD code to react to
> > and possibly collaborate to improve. So please let me know what you
> > think and/or fork it and send pull requests.
> > Answer yes to everything and start Solr before indexing EAD. (It uses
> > the Blacklight template from HEAD which allow extra head content.)
> > This code was just ripped out of our Historical State site [1] so lots
> > of NCSU specific code remains. Also, the intention in that application
> > was not to display everything possible in the EAD, but just to give a
> > the gist and refer the user to the full collection guide if they need
> > the full collection guide display [2]. Certainly more work could be
> > done to display more of the information.
> > --
> > You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
> > To post to this group, send email to blacklight-development@googlegroups.com.
> > To unsubscribe from this group, send email to blacklight-development+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/blacklight-development?hl=en.
> --
> You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
> To post to this group, send email to blacklight-development@googlegroups.com.
> To unsubscribe from this group, send email to blacklight-development+unsubscribe@googlegroups.com.
> For more options, visit this group athttp://groups.google.com/group/blacklight-development?hl=en.
-- You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
To post to this group, send email to blacklight-development@googlegroups.com.
To unsubscribe from this group, send email to blacklight-development+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/blacklight-development?hl=en.
On Tue, May 4, 2010 at 12:01 PM, adam wead <amsterda...@gmail.com> wrote:
> Well, I answered my own question...
> There's an option in Archivist's Toolkit that enables you to export
> numbered component levels. This did the trick.
> I'm sure I'll have more questions later, tho...
> On May 4, 11:49 am, adam wead <amsterda...@gmail.com> wrote:
>> Thanks for this, Jason. I installed a new application and it worked
>> great. I was able to index the sample EAD and MARC data, as well as
>> some LC marc records, the ead xml documents that come with the
>> blacklight app itelf, and an ead doc that I exported from Archivist's
>> Toolkit.
>> I have a question about displaying the contents of the ead files. The
>> README states that it only handles numbered parts of the collection
>> inventory. I believe the ead docs that I indexed that were not part
>> of the data set that came with your plugin do not use numbered parts
>> for their inventory. So, those documents do not display their
>> inventory, just the scope and content info. Is it possible to change
>> that? Or should I look into redoing the ead output from AT, for
>> example, to use numbered parts in the inventory.
>> Please feel free to point me the way to documentation on EAD formats,
>> or other relevant info. I'm relatively new to EAD, but I'd be
>> interested to know the issues behind inventory display in your
>> blacklight plugin.
>> thanks!
>> ...adam
>> On May 3, 5:33 pm, Jason Ronallo <jrona...@gmail.com> wrote:
>> > Hi,
>> > As promised earlier today during the call, I've released some very
>> > simple code for indexing and displaying EAD XML. I wanted to get this
>> > out there just so we'd have some other working EAD code to react to
>> > and possibly collaborate to improve. So please let me know what you
>> > think and/or fork it and send pull requests.
>> > Answer yes to everything and start Solr before indexing EAD. (It uses
>> > the Blacklight template from HEAD which allow extra head content.)
>> > This code was just ripped out of our Historical State site [1] so lots
>> > of NCSU specific code remains. Also, the intention in that application
>> > was not to display everything possible in the EAD, but just to give a
>> > the gist and refer the user to the full collection guide if they need
>> > the full collection guide display [2]. Certainly more work could be
>> > done to display more of the information.
>> > --
>> > You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
>> > To post to this group, send email to blacklight-development@googlegroups.com.
>> > To unsubscribe from this group, send email to blacklight-development+unsubscribe@googlegroups.com.
>> > For more options, visit this group athttp://groups.google.com/group/blacklight-development?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
>> To post to this group, send email to blacklight-development@googlegroups.com.
>> To unsubscribe from this group, send email to blacklight-development+unsubscribe@googlegroups.com.
>> For more options, visit this group athttp://groups.google.com/group/blacklight-development?hl=en.
> --
> You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
> To post to this group, send email to blacklight-development@googlegroups.com.
> To unsubscribe from this group, send email to blacklight-development+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/blacklight-development?hl=en.
-- You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
To post to this group, send email to blacklight-development@googlegroups.com.
To unsubscribe from this group, send email to blacklight-development+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/blacklight-development?hl=en.
