om 3.1.0 → 3.1.1

data/GETTING_STARTED.textile

@@ -1,254 +0,0 @@
-h2. OM (Opinionated Metadata) - Getting Started
-
-OM allows you to define a "terminology" to ease translation between XML and ruby objects - you can query the xml for Nodes _or_ node values without ever writing a line of XPath.
-
-OM "terms" are ruby symbols you define (in the terminology) that map specific XML content into ruby object attributes.
-
-The API documentation at "http://rdoc.info/github/projecthydra/om":http://rdoc.info/github/projecthydra/om provides additional, more targeted information.  We will provide links to the API as appropriate.
-
-h4. What you will learn from this document
-
-# Install OM and run it in IRB
-# Build an OM Terminology
-# Use OM XML Document class 
-# Create XML from the OM XML Document 
-# Load existing XML into an OM XML Document
-# Query OM XML Document to get term values
-# Access the Terminology of an OM XML Document
-# Retrieve XPath from the terminology
-
-
-h2. Install OM
-
-To get started, you will create a new folder, set up a Gemfile to install OM, and then run bundler.
-
-<pre>
-mkdir omtest
-cd omtest
-</pre>
-
-Using whichever editor you prefer, create a file (in omtest directory) called Gemfile with the following contents:
-
-<pre>
-source 'http://rubygems.org'
-gem 'om'
-</pre>
-
-Now run bundler to install the gem:  (you will need the bundler Gem)
-
-<pre>
-bundle install
-</pre>
-
-You should now be set to use irb to run the following example.
-
-h2. Build a simple OM terminology (in irb)
-
-To experiment with abbreviated terminology examples, irb is your friend.  If you are working on a persistent terminology and have to experiment to make sure you declare your terminology correctly, we recommend writing test code (e.g. with rspec).  You can see examples of this "here":https://github.com/projecthydra/hydra-tutorial-application/blob/master/spec/models/journal_article_mods_datastream_spec.rb 
-
-<pre>
-irb
-require "rubygems"
-=> true 
-require "om"
-=> true
-</pre>
-
-Create a simple (simplish?) Terminology Builder ("OM::XML::Terminology::Builder":OM/XML/Terminology/Builder.html") based on a couple of elements from the MODS schema.
-
-<pre>
-terminology_builder = OM::XML::Terminology::Builder.new 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")
-  # This is a mods:name.  The underscore is purely to avoid namespace conflicts.
-  t.name_ {
-    t.namePart
-    t.role(:ref=>[:role])
-    t.family_name(:path=>"namePart", :attributes=>{:type=>"family"})
-    t.given_name(:path=>"namePart", :attributes=>{:type=>"given"}, :label=>"first name")
-    t.terms_of_address(:path=>"namePart", :attributes=>{:type=>"termsOfAddress"})
-  }
-  
-  # Re-use the structure of a :name Term with a different @type attribute
-  t.person(:ref=>:name, :attributes=>{:type=>"personal"})
-  t.organization(:ref=>:name, :attributes=>{:type=>"corporate"})
-  
-  # This is a mods:role, which is used within mods:namePart elements
-  t.role {
-    t.text(:path=>"roleTerm",:attributes=>{:type=>"text"})
-    t.code(:path=>"roleTerm",:attributes=>{:type=>"code"})
-  }
-end
-</pre>
-
-Now tell the Terminology Builder to build your Terminology ("OM::XML::Terminology":OM/XML/Terminology.html"):
-
-<pre>terminology = terminology_builder.build</pre>
-
-h2. OM Documents
-
-Generally you will use an "OM::XML::Document":OM/XML/Document.html to work with your xml.  Here's how to define a Document class that uses the same Terminology as above.  
-
-In a separate window (so you can keep irb running), create the file my_mods_document.rb in the omtest directory, with this content:
-
-<pre>
-  class MyModsDocument &lt; ActiveFedora::NokogiriDatastream 
-    include OM::XML::Document
-    
-    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")
-      # This is a mods:name.  The underscore is purely to avoid namespace conflicts.
-      t.name_ {
-        t.namePart
-        t.role(:ref=>[:role])
-        t.family_name(:path=>"namePart", :attributes=>{:type=>"family"})
-        t.given_name(:path=>"namePart", :attributes=>{:type=>"given"}, :label=>"first name")
-        t.terms_of_address(:path=>"namePart", :attributes=>{:type=>"termsOfAddress"})
-      }
-      t.person(:ref=>:name, :attributes=>{:type=>"personal"})
-      t.organization(:ref=>:name, :attributes=>{:type=>"corporate"})
-
-      # This is a mods:role, which is used within mods:namePart elements
-      t.role {
-        t.text(:path=>"roleTerm",:attributes=>{:type=>"text"})
-        t.code(:path=>"roleTerm",:attributes=>{:type=>"code"})
-      }
-    end
-    
-    # Generates an empty Mods Article (used when you call ModsArticle.new without passing in existing xml)
-    #  (overrides default behavior of creating a plain xml document)
-    def self.xml_template
-      # use Nokogiri to build the XML
-      builder = Nokogiri::XML::Builder.new do |xml|
-        xml.mods(:version=>"3.3", "xmlns:xlink"=>"http://www.w3.org/1999/xlink",
-           "xmlns:xsi"=>"http://www.w3.org/2001/XMLSchema-instance",
-           "xmlns"=>"http://www.loc.gov/mods/v3",
-           "xsi:schemaLocation"=>"http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd") {
-             xml.titleInfo(:lang=>"") {
-               xml.title
-             }
-             xml.name(:type=>"personal") {
-               xml.namePart(:type=>"given")
-               xml.namePart(:type=>"family")
-               xml.affiliation
-               xml.computing_id
-               xml.description
-               xml.role {
-                 xml.roleTerm("Author", :authority=>"marcrelator", :type=>"text")
-               }
-             }
-           }
-      end
-      # return a Nokogiri::XML::Document, not an OM::XML::Document
-      return builder.doc
-    end
-    
-  end
-</pre>
-
-(Note that we are now also using the ActiveFedora gem.)
-
-"OM::XML::Document":OM/XML/Document.html provides the set_terminology method to handle the details of creating a TerminologyBuilder and building the terminology for you.  This allows you to focus on defining the structures of the Terminology itself.
-
-h3. Creating XML Documents from Scratch using OM
-
-By default, new OM Document instances will create an empty xml document, but if you override self.xml_template to return a different object (e.g. "Nokogiri::XML::Document":http://nokogiri.rubyforge.org/nokogiri/Nokogiri/XML/Document.html), that will be created instead.  
-
-In the example above, we have overridden xml_template to build an empty, relatively simple MODS document as a "Nokogiri::XML::Document":http://nokogiri.rubyforge.org/nokogiri/Nokogiri/XML/Document.html.  We use "Nokogiri::XML::Builder":http://nokogiri.rubyforge.org/nokogiri/Nokogiri/XML/Builder.html and call its .doc method at the end of xml_template in order to return the "Nokogiri::XML::Document":http://nokogiri.rubyforge.org/nokogiri/Nokogiri/XML/Document.html object.  Instead of using "Nokogiri::XML::Builder":http://nokogiri.rubyforge.org/nokogiri/Nokogiri/XML/Builder.html, you could put your template into an actual xml file and have xml_template use "Nokogiri::XML::Document.parse":http://nokogiri.rubyforge.org/nokogiri/Nokogiri/XML/Document.html#M000225 to load it.  That's up to you.  Create the documents however you want, just return a "Nokogiri::XML::Document":http://nokogiri.rubyforge.org/nokogiri/Nokogiri/XML/Document.html.
-
-to use "Nokogiri::XML::Builder":http://nokogiri.rubyforge.org/nokogiri/Nokogiri/XML/Builder.html
-
-<pre>
-require "my_mods_document"
-newdoc = MyModsDocument.new
-newdoc.to_xml
-=> NoMethodError: undefined method `to_xml' for nil:NilClass
-</pre>
-
-
-h3. Loading an existing XML document with OM
-
-To load existing XML into your OM Document, use "#from_xml":OM/XML/Container/ClassMethods.html#from_xml-instance_method"
-
-For an example, download "hydrangea_article1.xml":https://github.com/mediashelf/om/blob/master/spec/fixtures/mods_articles/hydrangea_article1.xml into your working directory (omtest), then run this in irb:
-
-<pre>
-sample_xml = File.new("hydrangea_article1.xml")
-doc = MyModsDocument.from_xml(sample_xml)
-</pre>
-
-Take a look at the document object's xml that you've just populated.  We will use this document for the next few examples.
-
-<pre>doc.to_xml</pre>
-
-h3. Querying OM Documents 
-
-Using the Terminology associated with your Document, you can query the xml for nodes _or_ node values without ever writing a line of XPath.
-
-You can use OM::XML::Document.find_by_terms to retrieve xml _nodes_ from the datastream.  It returns Nokogiri::XML::Node objects:
-
-<pre>
-doc.find_by_terms(:person)
-doc.find_by_terms(:person).length
-doc.find_by_terms(:person).each {|n| puts n.to_xml}
-</pre>
-
-You might prefer to use nodes as a way of getting multiple values pertaining to a node, rather than doing more expensive lookups for each desired value.
-
-If you want to get directly to the _values_ within those nodes, use OM::XML::Document.term_values:
-
-<pre>
-doc.term_values(:person, :given_name)
-doc.term_values(:person, :family_name)
-</pre>
-
-If the xpath points to XML nodes that contain other nodes, the response to term_values will contain Nokogiri::XML::Node objects instead of text values:
-
-<pre>
-doc.term_values(:name)
-</pre>
-
-For more examples of Querying OM Documents, see "Querying Documents":https://github.com/mediashelf/om/blob/master/QUERYING_DOCUMENTS.textile
-
-h3. Updating, Inserting & Deleting Elements (TermValueOperators)
-
-For more examples of Updating OM Documents, see "Updating Documents":https://github.com/mediashelf/om/blob/master/UPDATING_DOCUMENTS.textile
-
-h3. Validating Documents
-
-If you have an XML schema defined in your Terminology's root Term, you can validate any xml document by calling ".validate" on any instance of your Document classes.
-
-<pre>doc.validate</pre>
-
-__*Note:* this method requires an internet connection, as it will download the XML schema from the URL you have specified in the Terminology's root term.__
-
-h3. Directly accessing the "Nokogiri::XML::Document":http://nokogiri.rubyforge.org/nokogiri/Nokogiri/XML/Document.html and the "OM::XML::Terminology":https://github.com/mediashelf/om/blob/master/lib/om/xml/terminology.rb
-
-"OM::XML::Document":https://github.com/mediashelf/om/blob/master/lib/om/xml/document.rb is implemented as a container for a "Nokogiri::XML::Document":http://nokogiri.rubyforge.org/nokogiri/Nokogiri/XML/Document.html.  It uses the associated OM Terminology to provide a bunch of convenience methods that wrap calls to Nokogiri.  If you ever need to operate directly on the Nokogiri Document, simply call ng_xml and do what you need to do.  OM will not get in your way.
-
-<pre>ng_document = doc.ng_xml</pre>
-
-If you need to look at the Terminology associated with your Document, call "#terminology":OM/XML/Document/ClassMethods.html#terminology-instance_method on the Document's _class_.
-
-<pre>
-MyModsDocument.terminology
-doc.class.terminology
-</pre>
-
-h2. Using a Terminology to generate XPath Queries based on Term Pointers 
-
-Because the Terminology is essentially a mapping from XPath queries to ruby object attributes, in most cases you won't need to know the actual XPath queries.  Nevertheless, when you <i>do</i> want to know the Xpath (e.g. for ensuring your terminology is correct) for a term, the Terminology can generate xpath queries based on the structures you've defined ("OM::XML::TermXPathGenerator":OM/XML/TermXpathGenerator.html).
-
-Here are the xpaths for :name and two variants of :name that were created using the :ref argument in the Terminology Builder:
-
-<pre>
-terminology.xpath_for(:name)
-=> "//oxns:name"
-terminology.xpath_for(:person)
-=> "//oxns:name[@type=\"personal\"]" 
-terminology.xpath_for(:organization)
-=> "//oxns:name[@type=\"corporate\"]"
-</pre>
-
-h2. Solrizing Documents
-
-The solrizer gem provides support for indexing XML documents into Solr based on OM Terminologies.  That process is documented in the "solrizer documentation":http://rdoc.info/github/projecthydra/solrizer

data/History.textile

@@ -1,186 +0,0 @@
-h3. 3.1.0 (17 Jul 2014)
-  2014-07-17: Bump solrizer version to ~> 3.3 [Justin Coyne]
-
-  2014-07-17: Use the system libxml2 on travis [Justin Coyne]
-
-  2014-07-17: Remove dependency on mediashelf-loggable [Justin Coyne]
-
-  2014-06-13: Setting values on a proxy term should build the parent terms if they
-  don't exist [Justin Coyne]
-
-  2014-06-05: Handle invalid time for Rails 3 [Justin Coyne]
-
-  2014-06-02: Updating solrizer, correcting rspec deprecations [Adam Wead]
-
-h3. 3.0.1 (25 Jun 2013)
-  Fix bug where values that were the same as the existing values were 
-    removed from the update list
-
-h3. 3.0.0 (20 Jun 2013)
-  Return an array instead of a hash Term#update_values
-  When passing an array to Term#update_values, it will overwrite all of
-    the existing values of that term.
-  OM::XML::Document#find_by_terms_and_value should match strings with 
-    text() = xpath query, rather than contains().  
-
-h3. 2.2.1 (20 Jun 2013)
-  Revert deprecation of passing Hash values
-
-h3. 2.2.0 (20 June 2013)
-  Deprecate passing Hash values into DynamicNode#val= or 
-  Document#update_attributes. This behavior will be removed in 3.0.0
-  Rails 4 support
-  Pass nil in order to remove a node (instead of blank string)
-
-h3. 2.1.2 (3 May 2013)
-  Fix missing comma after exception
-
-h3. 2.1.1 (2 May 2013)
-  bump solrizer to 3.1.0
-
-h3. 2.1.0 (29 April 2013)
-  support for element names with periods in them
-  support for 'type: :time'
-  
-
-h3. 2.0.0
-  Support new solr schema
-
-h3. 1.8.0
-  Removed unused mods_article_terminology.xml
-  Replacing :data_type with :type; deprecating :data_type
-  Making test related to HYDRA-647 pending
-  Adding .type method for ruby 1.8.7 compatibility
-  XML serialization should use the data_type node name and not type
-  Update homepage in gemspec
-  Remove .rvmrc
-  Remove debugger from gemfile
-
-h3. 1.7.0
-  Add casting to dates and integers when you specify the :type attribute on a terminology node
-
-h3. 1.6.1
-  Integration spec to illustrate selective querying.
-  Add #use_terminology and #extend_terminology methods to extend existing OM terminologies
-
-h3. 1.6.0
-  Delegate all methods on the dynamic node to the found values
-  Allow arrays to be set on dynamic nodes
-
-h3. 1.5.3
-
-  HYDRA-657 OM Terms that share a name with methods on Nokogiri Builders have incorrect builder templates
-  HYDRA-674 XML Builder templates incorrect for :none attributes
-
-h3. 1.5.2
-
-  HYDRA-742 Can't modify frozen string (parameters in rails 3.2, when using ruby 1.9.3)
-
-h3. 1.5.1
-
-  HYDRA-737 OM tests fail under ree 1.8.7-2011.12
-  (Fix also applies to ruby 1.8.7-p357)
-  
-h3. 1.5.0
-
-  HYDRA-358 Added support for namespaceless terminologies
-
-h3. 1.4.4
-
-  HYDRA-415 https://jira.duraspace.org/browse/HYDRA-415 Fixed insert of attribute nodes
-  update to rspec2
-  compatibility fixes for ruby 1.9
-  RedCloth updated to 4.2.9
-  Replace local 'delimited_list' logic with Array#join
-
-h3. 1.4.3
-
-  HYDRA-681 https://jira.duraspace.org/browse/HYDRA-681 Om was calling .dirty when updating nodes, it should only do that when it's operating on a Nokogiri:Datastream
-  HYDRA-682 https://jira.duraspace.org/browse/HYDRA-682 Om first level terms support update
-
-h3. 1.4.2
-  
-  "HYDRA-667":https://jira.duraspace.org/browse/HYDRA-667 Fixed bug where updating nodes wasn't marking the document as dirty
-
-h3. 1.4.0
-
-  Added dynamic node access DSL. Added a warning when calling an index on a proxy term.
-
-h3. 1.3.0
-
-  Document automatically includes Validation module, meaning that you can now call .validate on any document
-
-h3. 1.2.4
-
-  TerminologyBuilder.root now passes on its options to the root term builder that it creates.
-
-h3. 1.2.3
-
-  NamedTermProxies can now point to terms at the root of a Terminology
-
-h3. 1.2.0
-
-  added OM::XML::TemplateRegistry for built-in templating and creation of new XML nodes
-
-h3. 1.1.1
-   
-  "HYDRA-395":https://jira.duraspace.org/browse/HYDRA-395: Fixed bug that prevented you from appending term values with apostrophes in them
-
-h2. 1.1.0
-
-HYDRA-371: Provide a way to specify a term that points to nodes where an attribute is not set
-
-  Add support for this syntax in Terminologies, where an attribute value can be :none.  When an attribute's value is set to :none, a not() predicate is used in the resulting xpath 
-
-    t.computing_id(:path=>"namePart", :attributes=>{:type=>:none}) 
-    
-    will result in an xpath that looks like:
-    
-    //namePart[not(@type)] 
-
-namePart[not(@type)]
-
-h3. 1.0.1
-
-HYDRA-329: Allow for NamedTermProxies at root of Terminology
-
-h2. 1.0.0
-
-Stable release 
-
-h3. 0.1.10
-
-Improving generation of constrained xpath queries
-
-h3. 0.1.9
-
-Improving support for deeply nested nodes (still needs work though)
-
-h3. 0.1.5
-
-* root_property now inserts an entry into the properties hash
-* added .generate method for building new instances of declared properties
-* refinements to accessor_xpath
-
-h3. 0.1.4
-
-*  made attribute_xpath idempotent
-
-h3. 0.1.3
-
-*  added accessor_generic_name and accessor_hierarchical_name methods
-
-h3. 0.1.2
-
-* changed syntax for looking up accessors with (optional) index values -- no using [{:person=>1}, :first_name]  instead of [:person, 1, :first_name]
-
-h3. 0.1.1
-
-RENAMED to om (formerly opinionated-xml)
-
-* broke up functionality into Modules
-* added OM::XML::Accessor functionality
-
-h3. 0.1
-
-Note: OX v.1 Does not handle treating attribute values as the changing "value" of a node

data/QUERYING_DOCUMENTS.textile

@@ -1,139 +0,0 @@
-h2. Querying OM Documents
-
-This document will help you understand how to access the information associated with an "OM::XML::Document":OM/XML/Document.html object.  We will explain some of the methods provided by the "OM::XML::Document":OM/XML/Document.html module and its related modules "OM::XML::TermXPathGenerator":OM/XML/TermXPathGenerator.html & "OM::XML::TermValueOperators":OM/XML/TermValueOperators.html
-
-_Note: In your code, don't worry about including OM::XML::TermXPathGenerator and OM::XML::TermValueOperators into your classes.  OM::XML::Document handles that for you._
-
-h3. Load the Sample XML and Sample Terminology
-
-These examples use the Document class defined in "OM::Samples::ModsArticle":https://github.com/mediashelf/om/blob/master/lib/om/samples/mods_article.rb
-
-Download "hydrangea_article1.xml":https://github.com/mediashelf/om/blob/master/spec/fixtures/mods_articles/hydrangea_article1.xml (sample xml) into your working directory, then run this in irb:
-
-<pre>
-  require "om/samples"
-  sample_xml = File.new("hydrangea_article1.xml")
-  doc = OM::Samples::ModsArticle.from_xml(sample_xml)
-</pre>
-
-h2. Querying the "OM::XML::Document":OM/XML/Document.html
-
-The "OM::XML::Terminology":OM/XML/Terminology.html" declared by "OM::Samples::ModsArticle":https://github.com/mediashelf/om/blob/master/lib/om/samples/mods_article.rb maps the defined Terminology structure to xpath queries.  It will also run the queries for you in most cases.  
-
-h4. xpath_for method of "OM::XML::Terminology":OM/XML/Terminology.html" retrieves xpath expressions for OM terms
-
-The xpath_for method retrieves the xpath used by the "OM::XML::Terminology":OM/XML/Terminology.html"
-
-Examples of xpaths for :name and two variants of :name that were created using the :ref argument in the Terminology builder:
-
-<pre>
-OM::Samples::ModsArticle.terminology.xpath_for(:name)
-=> "//oxns:name"
-OM::Samples::ModsArticle.terminology.xpath_for(:person)
-=> "//oxns:name[@type=\"personal\"]" 
-OM::Samples::ModsArticle.terminology.xpath_for(:organization)
-=> "//oxns:name[@type=\"corporate\"]"
-</pre>
-
-h4. Working with Terms
-
-To retrieve the values of xml nodes, use the term_values method:
-
-<pre>
-doc.term_values(:person, :first_name) 
-doc.term_values(:person, :last_name) 
-</pre>
-
-The term_values method is defined in the "OM::XML::TermValueOperators":OM/XML/TermValueOperators.html module, which is included in "OM::XML::Document":OM/XML/Document.html
-
-Not that if a term's xpath mapping points to XML nodes that contain other nodes, the response to term_values will be Nokogiri::XML::Node objects instead of text values:
-
-<pre>
-  doc.term_values(:name)
-</pre>
-
-More examples of using term_values and find_by_terms (defined in "OM::XML::Document":OM/XML/Document.html):
-
-<pre>
-doc.find_by_terms(:organization).to_xml
-doc.term_values(:organization, :role)
-=> ["\n      Funder\n    "] 
-doc.term_values(:organization, :namePart)
-=> ["NSF"]
-</pre>
-
-To retrieve the values of nested terms, create a sequence of terms, from outermost to innermost:
-
-<pre>
-OM::Samples::ModsArticle.terminology.xpath_for(:journal, :issue, :pages, :start)
-=> "//oxns:relatedItem[@type=\"host\"]/oxns:part/oxns:extent[@unit=\"pages\"]/oxns:start" 
-doc.term_values(:journal, :issue, :pages, :start)
-=> ["195"] 
-</pre>
-  
-If you get one of the term names wrong in the sequence, OM will tell you which one is causing problems.  See what happens when you put :page instead of :pages in your argument to term_values.
-
-<pre>
-doc.term_values(:journal, :issue, :page, :start)
-OM::XML::Terminology::BadPointerError: You attempted to retrieve a Term using this pointer: [:journal, :issue, :page] but no Term exists at that location. Everything is fine until ":page", which doesn't exist.
-</pre>
-
-
-h2. When XML Elements are Reused in a Document
-
-(Another way to put this: the xpath statement for a term can be ambiguous.)
-
-In our MODS document, we have two distinct uses of the title XML element:
-# the title of the published article 
-# the title of the journal it was published in.  
-
-How can we distinguish between these two uses?
-
-<pre>
-doc.term_values(:title_info, :main_title)
-=> ["ARTICLE TITLE", "VARYING FORM OF TITLE", "TITLE OF HOST JOURNAL"] 
-doc.term_values(:mods, :title_info, :main_title)
-=> ["ARTICLE TITLE", "VARYING FORM OF TITLE"]
-OM::Samples::ModsArticle.terminology.xpath_for(:title_info, :main_title)
-=> "//oxns:titleInfo/oxns:title" 
-</pre>
-
-The solution: include the root node in your term pointer.
-
-<pre>
-OM::Samples::ModsArticle.terminology.xpath_for(:mods, :title_info, :main_title)
-=> "//oxns:mods/oxns:titleInfo/oxns:title"
-doc.term_values(:mods, :title_info, :main_title)
-=> ["ARTICLE TITLE", "VARYING FORM OF TITLE"] 
-</pre>
-
-We can still access the Journal title by its own pointers:
-
-<pre>
-doc.term_values(:journal, :title_info, :main_title)
- => ["TITLE OF HOST JOURNAL"] 
-</pre>
-
-h2. Making life easier with Proxy Terms
-
-If you use a nested term often, you may want to avoid typing the whole sequence of term names by defining a _proxy_ term.  
-
-As you can see in "OM::Samples::ModsArticle":https://github.com/mediashelf/om/blob/master/lib/om/samples/mods_article.rb, we have defined a few proxy terms for convenience.
-
-<pre>
-t.publication_url(:proxy=>[:location,:url])
-t.peer_reviewed(:proxy=>[:journal,:origin_info,:issuance], :index_as=>[:facetable])
-t.title(:proxy=>[:mods,:title_info, :main_title])
-t.journal_title(:proxy=>[:journal, :title_info, :main_title])
-</pre>
-
-You can use proxy terms just like any other term when querying the document.
-
-<pre>
-OM::Samples::ModsArticle.terminology.xpath_for(:peer_reviewed)
-=> "//oxns:relatedItem[@type=\"host\"]/oxns:originInfo/oxns:issuance"
-OM::Samples::ModsArticle.terminology.xpath_for(:title)
-=> "//oxns:mods/oxns:titleInfo/oxns:title" 
-OM::Samples::ModsArticle.terminology.xpath_for(:journal_title)
-=> "//oxns:relatedItem[@type=\"host\"]/oxns:titleInfo/oxns:title"
-</pre>