active-fedora 2.2.0 → 2.2.1

data/NG_XML_DATASTREAM.textile

@@ -1,25 +0,0 @@
-h1. Setting the XML in a NokogiriDatastream from a file
-
-h2. Setting the Datastream's XML
-
-We will make this smoother soon, but right now you have to manually parse your new xml as a Nokogiri XML Document and then put the Nokogiri Document in the datastream's ng_xml attribute.
-
-Example (you will have to change the path to point to the xml file you want)
-
-<pre>
-my_path = "../om/spec/fixtures/mods_articles/hydrangea_article1.xml"
-f = File.new(my_path)
-xml = Nokogiri::XML::Document.parse(f)
-ha = HydrangeaArticle.new
-ha.datastreams["descMetadata"].to_xml
-ha.datastreams["descMetadata"].ng_xml = xml
-ha.datastreams["descMetadata"].to_xml
-</pre>
-
-h2. Saving the Datastream
-
-In order to make sure that your updated datastream is saved to fedora, call .save _on the datastream_.  If you call .save on the _object_, the changes you've made to the datastream might not be saved.
-
-<pre>
-ha.datastreams["descMetadata"].save
-</pre>

data/USING_OM_DATASTREAMS.textile

@@ -1,60 +0,0 @@
-h1. Using OM-based NokogiriDatastreams
-
-h2. Setup
-
-This tutorial assumes that you've run script/console from the root of Hydrangea and have imported Hydrangea's fixtures.
-
-The HydrangeaArticle model definition is located at https://github.com/projecthydra/hydrangea/blob/master/vendor/plugins/hydrangea_articles/app/models/hydrangea_article.rb
-
-Look in the "Hydra::ModsArticle":https://github.com/projecthydra/hydrangea/blob/master/vendor/plugins/hydra_repository/lib/hydra/mods_article.rb and "Hydra::RightsMetadata":https://github.com/projecthydra/hydrangea/blob/master/vendor/plugins/hydra_repository/lib/hydra/rights_metadata.rb" datastream definitions to see the OM Terminologies they define.
-
-h2. The Tour
-
-First, create some objects to play around with.
-
-<pre>
-ha = HydrangeaArticle.new
-fixture_article = HydrangeaArticle.load_instance("hydrangea:fixture_mods_article1")
-<pre>
-
-<pre>
-ha.datastreams.keys
-fixture_article.datastreams.keys
-</pre>
-
-Each datastream is associated with a class that is aware of its content.  These classes are specified in the model.  
-
-<pre>
-ha.datastreams["rightsMetadata"].class
-ha.datastreams["descMetadata"].class
-<pre>
-  
-You can retrieve the xml from the object as xml (string) using to_xml, or you can access it as a Nokogiri::XML::Document using .ng_xml
-
-<pre>
-ha.datastreams["rightsMetadata"].to_xml
-ha.datastreams["rightsMetadata"].ng_xml.class
-</pre>
-
-FYI, an OM terminology is attached to the datastream's class.  OM's convenience methods use the terminology to look up nodes and values for you.
-
-<pre>
-ha.datastreams["rightsMetadata"].class.terminology
-</pre>
-
-The ModsArticle Terminology lets you retrieve values from the descMetadata datastream's MODS content.
-
-<pre>
-fixture_mods_ds = fixture_article.datastreams["descMetadata"]
-fixture_mods_ds.term_values(:person, :first_name)
-fixture_mods_ds.term_values(:person, :last_name)
-</pre>
-
-You can use OM's find_by_terms method to retrieve xml nodes from the datastream.  It returns Nokogiri::XML::Node objects.
-
-<pre>
-fixture_mods_ds.find_by_terms(:person)
-fixture_mods_ds.find_by_terms(:person).length
-fixture_mods_ds.find_by_terms(:person).each {|n| puts n.to_xml}
-</pre>
-  

data/VERSION

@@ -1 +0,0 @@
-2.2.0

data/lib/hydra.rb

@@ -1,2 +0,0 @@
-module Hydra;end
-require "hydra/sample_mods_datastream"

data/lib/hydra/sample_mods_datastream.rb

@@ -1,63 +0,0 @@
-require "hydra"
-module Hydra
-class Hydra::SampleModsDatastream < ActiveFedora::NokogiriDatastream       
-    
-    set_terminology do |t|
-      t.root(:path=>"mods", :xmlns=>"http://www.loc.gov/mods/v3", :schema=>"http://www.loc.gov/standards/mods/v3/mods-3-2.xsd")
-
-      t.title_info(:path=>"titleInfo") {
-        t.main_title(:path=>"title", :label=>"title")
-        t.language(:path=>{:attribute=>"lang"})
-      } 
-      t.abstract     
-      t.topic_tag(:path=>"subject", :default_content_path=>"topic")           
-      # This is a mods:name.  The underscore is purely to avoid namespace conflicts.
-      t.name_ {
-        # this is a namepart
-        t.namePart(:index_as=>[:searchable, :displayable, :facetable, :sortable], :required=>:true, :type=>:string, :label=>"generic name")
-        # affiliations are great
-        t.affiliation
-        t.displayForm
-        t.role(:ref=>[:role])
-        t.description
-        t.date(:path=>"namePart", :attributes=>{:type=>"date"})
-        t.last_name(:path=>"namePart", :attributes=>{:type=>"family"})
-        t.first_name(:path=>"namePart", :attributes=>{:type=>"given"}, :label=>"first name")
-        t.terms_of_address(:path=>"namePart", :attributes=>{:type=>"termsOfAddress"})
-      }
-      # lookup :person, :first_name        
-      t.person(:ref=>:name, :attributes=>{:type=>"personal"})
-      t.organizaton(:ref=>:name, :attributes=>{:type=>"institutional"})
-      t.conference(:ref=>:name, :attributes=>{:type=>"conference"})
-
-      t.role {
-        t.text(:path=>"roleTerm",:attributes=>{:type=>"text"})
-        t.code(:path=>"roleTerm",:attributes=>{:type=>"code"})
-      }
-      t.journal(:path=>'relatedItem', :attributes=>{:type=>"host"}) {
-        t.title_info
-        t.origin_info(:path=>"originInfo") {
-          t.publisher
-          t.date_issued(:path=>"dateIssued")
-        }
-        t.issn(:path=>"identifier", :attributes=>{:type=>"issn"})
-        t.issue(:path=>"part") {
-          t.volume(:path=>"detail", :attributes=>{:type=>"volume"}, :default_content_path=>"number")
-          t.level(:path=>"detail", :attributes=>{:type=>"number"}, :default_content_path=>"number")
-          t.extent
-          t.pages(:path=>"extent", :attributes=>{:type=>"pages"}) {
-            t.start
-            t.end
-          }
-          t.publication_date(:path=>"date")
-        }
-      }
-      
-    end
-    
-    # Changes from OM::Properties implementation
-    # renamed family_name => last_name
-    # start_page & end_page now accessible as [:journal, :issue, :pages, :start] (etc.)
-
-end
-end

data/tasks/rspec.rake

@@ -1,29 +0,0 @@
-begin
-  require 'spec'
-rescue LoadError
-  require 'rubygems'
-  require 'spec'
-end
-begin
-  require 'spec/rake/spectask'
-rescue LoadError
-  puts <<-EOS
-To use rspec for testing you must install rspec gem:
-    gem install rspec
-EOS
-  exit(0)
-end
-
-desc "Run the specs under spec/models"
-Spec::Rake::SpecTask.new do |t|
-  t.spec_opts = ['--options', "spec/spec.opts"]
-  t.spec_files = FileList['spec/**/*_spec.rb']
-end
-
-namespace :spec do
-  desc "run the unit specs"
-  Spec::Rake::SpecTask.new(:units) do |t|
-    t.spec_opts = ['--options', "spec/spec.opts"]
-    t.spec_files = FileList['spec/unit/**/*_spec.rb']
-  end
-end