hydra-validations 0.0.1 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: a47a19ff9228aa10cfe83244e932a14d1e7de081
-  data.tar.gz: 48f15f4febd8af91c1c31277c36e8bb8b3d2d062
+  metadata.gz: 435663a78ed5e8ae4eed2d29cebbee6860792ed2
+  data.tar.gz: 85cf53d256c12174cda539c5193afff0a0e08a8a
 SHA512:
-  metadata.gz: 2eda85501b41be48d7a016382dc37ed5bf9313a25813f6ca71f775adc75e94ac7d472a6aa7ce303a1c8718635baebb9e6c9ba2d827ecc236437c44f4eff14bef
-  data.tar.gz: 54bdcb0cba015b4341f3410b43f2e9c2ee8b95d95069e34fc65f5e8a2194beda8cdd87dc94a9e7e3ace81529e001dff0af22d64b9a0784cc750dc12b8bac93cf
+  metadata.gz: cb3a7917caf907655fdfdcb3f1f304294c1cd4ea32abd73792b4301ac5b889b07a5c88e78c5519d8de86666c6d7419559fc6cbe3e82345cc81d16de833f9dd35
+  data.tar.gz: 906c190556c2aecb9ecd23c9dc123398551725f032b0616481d497d956b5382ce56c116da718b21d882641de370348e2d9085a0a3a0e68b57be913db79c5b5cb

data/.gitignore

@@ -1,5 +1,5 @@
-.rspec
 /tmp
 /spec/tmp
 /.bundle
+/pkg
 Gemfile.lock

data/.rspec

@@ -0,0 +1 @@
+--color

data/.travis.yml

@@ -0,0 +1,5 @@
+language: ruby
+rvm:
+  - 1.9.3
+  - 2.0.0
+  - 2.1

data/CONTRIBUTING.md

@@ -0,0 +1,116 @@
+# How to Contribute
+
+We want your help to make Project Hydra great.
+There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
+
+## Hydra Project Intellectual Property Licensing and Ownership
+
+All code contributors must have an Individual Contributor License Agreement (iCLA) on file with the Hydra Project Steering Group.
+If the contributor works for an institution, the institution must have a Corporate Contributor License Agreement (cCLA) on file.
+
+https://wiki.duraspace.org/display/hydra/Hydra+Project+Intellectual+Property+Licensing+and+Ownership
+
+You should also add yourself to the `CONTRIBUTORS.md` file in the root of the project.
+
+## Contribution Tasks
+
+* Reporting Issues
+* Making Changes
+* Submitting Changes
+* Merging Changes
+
+### Reporting Issues
+
+* Make sure you have a [GitHub account](https://github.com/signup/free)
+* Submit a [Github issue](./issues) by:
+  * Clearly describing the issue
+    * Provide a descriptive summary
+    * Explain the expected behavior
+    * Explain the actual behavior
+    * Provide steps to reproduce the actual behavior
+
+### Making Changes
+
+* Fork the repository on GitHub
+* Create a topic branch from where you want to base your work.
+  * This is usually the master branch.
+  * To quickly create a topic branch based on master; `git branch fix/master/my_contribution master`
+  * Then checkout the new branch with `git checkout fix/master/my_contribution`.
+  * Please avoid working directly on the `master` branch.
+  * You may find the [hub suite of commands](https://github.com/defunkt/hub) helpful
+* Make commits of logical units.
+  * Your commit should include a high level description of your work in HISTORY.textile 
+* Check for unnecessary whitespace with `git diff --check` before committing.
+* Make sure your commit messages are [well formed](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+* If you created an issue, you can close it by including "Closes #issue" in your commit message. See [Github's blog post for more details](https://github.com/blog/1386-closing-issues-via-commit-messages)
+
+```
+    Present tense short summary (50 characters or less)
+
+    More detailed description, if necessary. It should be wrapped to 72
+    characters. Try to be as descriptive as you can, even if you think that
+    the commit content is obvious, it may not be obvious to others. You
+    should add such description also if it's already present in bug tracker,
+    it should not be necessary to visit a webpage to check the history.
+
+    Include Closes #<issue-number> when relavent.
+
+    Description can have multiple paragraphs and you can use code examples
+    inside, just indent it with 4 spaces:
+
+        class PostsController
+          def index
+            respond_with Post.limit(10)
+          end
+        end
+
+    You can also add bullet points:
+
+    - you can use dashes or asterisks
+
+    - also, try to indent next line of a point for readability, if it's too
+      long to fit in 72 characters
+```
+
+* Make sure you have added the necessary tests for your changes.
+* Run _all_ the tests to assure nothing else was accidentally broken.
+* When you are ready to submit a pull request
+
+### Submitting Changes
+
+[Detailed Walkthrough of One Pull Request per Commit](http://ndlib.github.io/practices/one-commit-per-pull-request/)
+
+* Read the article ["Using Pull Requests"](https://help.github.com/articles/using-pull-requests) on GitHub.
+* Make sure your branch is up to date with its parent branch (i.e. master)
+  * `git checkout master`
+  * `git pull --rebase`
+  * `git checkout <your-branch>`
+  * `git rebase master`
+  * It is likely a good idea to run your tests again.
+* Squash the commits for your branch into one commit
+  * `git rebase --interactive HEAD~<number-of-commits>` ([See Github help](https://help.github.com/articles/interactive-rebase))
+  * To determine the number of commits on your branch: `git log master..<your-branch> --oneline | wc -l`
+  * Squashing your branch's changes into one commit is "good form" and helps the person merging your request to see everything that is going on.
+* Push your changes to a topic branch in your fork of the repository.
+* Submit a pull request from your fork to the project.
+
+### Merging Changes
+
+* It is considered "poor from" to merge your own request.
+* Please take the time to review the changes and get a sense of what is being changed. Things to consider:
+  * Does the commit message explain what is going on?
+  * Does the code changes have tests? _Not all changes need new tests, some changes are refactorings_
+  * Does the commit contain more than it should? Are two separate concerns being addressed in one commit?
+  * Did the Travis tests complete successfully?
+* If you are uncertain, bring other contributors into the conversation by creating a comment that includes their @username.
+* If you like the pull request, but want others to chime in, create a +1 comment and tag a user.
+
+## New Developers
+A great way to get new developers involved and to learn the process is to have them go through the Hierarchy of Promises and create a pull request to improve it.
+
+# Additional Resources
+
+* [General GitHub documentation](http://help.github.com/)
+* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
+* [Pro Git](http://git-scm.com/book) is both a free and excellent book about Git.
+* [A Git Config for Contributing](http://ndlib.github.io/practices/my-typical-per-project-git-config/)

data/CONTRIBUTORS.md

@@ -0,0 +1,3 @@
+Contributors to this project:
+
+* David Chandek-Stark

data/LICENSE

@@ -1,201 +1,14 @@
-Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
+Copyright 2014 Duke University Libraries
+Additional copyright may be held by others, as reflected in the commit log.
 
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
 
-   1. Definitions.
+    http://www.apache.org/licenses/LICENSE-2.0
 
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "{}"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright {yyyy} {name of copyright owner}
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/README.md

@@ -1,7 +1,13 @@
 hydra-validations
 =======================
 
-Custom validations for Hydra applications based on ActiveModel::Validations.
+Custom validators for Hydra applications based on ActiveModel::Validations.
+
+### Dependencies
+
+* Ruby >= 1.9.3
+* ActiveModel 4.x
+* ActiveFedora 7.x
 
 ### Installation
 
@@ -17,16 +23,33 @@ and
 bundle install
 ```
 
-### Usage
-
-To include helper methods:
-
-```ruby
-include Hydra::Validations
-```
+### Example
 
-For example:
+With a PORO, we have to include ActiveModel::Validations.  
+ActiveRecord::Base and ActiveFedora::Base already include ActiveModel::Validations.
 
 ```ruby
-validates_single_cardinality_of :my_single_valued_attr
+class Validatable
+  include ActiveModel::Validations 
+  include Hydra::Validations
+  attr_accessor :field
+  validates :field, single_cardinality: true
+end
+
+> Validatable.validators
+ => [#<Hydra::Validations::SingleCardinalityValidator:0x007fb91d1e9460 @attributes=[:field], @options={}>] 
+> v = Validatable.new
+ => #<Validatable:0x007fb91d1c9188> 
+> v.field = "foo"
+ => "foo" 
+> v.valid?
+ => true 
+> v.field = ["foo"]
+ => ["foo"] 
+> v.valid?
+ => true 
+> v.field = ["foo", "bar"]
+ => ["foo", "bar"] 
+> v.valid?
+ => false 
 ```

data/Rakefile

@@ -1,2 +1,6 @@
 require "bundler/gem_tasks"
+require "rspec/core/rake_task"
 
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/hydra-validations.gemspec

@@ -6,12 +6,14 @@ require 'hydra/validations/version'
 Gem::Specification.new do |spec|
   spec.name          = "hydra-validations"
   spec.version       = Hydra::Validations::VERSION
+  spec.platform      = Gem::Platform::RUBY
   spec.authors       = ["dchandekstark"]
   spec.email         = ["dchandekstark@gmail.com"]
   spec.summary       = %q{Validations for Hydra applications, based on ActiveModel::Validations}
   spec.description   = %q{Validations for Hydra applications, based on ActiveModel::Validations}
   spec.homepage      = "https://github.com/duke-libraries/hydra-validations"
   spec.license       = "APACHE2"
+  spec.required_ruby_version = ">= 1.9.3"
 
   spec.files         = `git ls-files -z`.split("\x0")
   spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
@@ -19,6 +21,7 @@ Gem::Specification.new do |spec|
   spec.require_paths = ["lib", "app/validators"]
 
   spec.add_dependency "activemodel", "~> 4.0"
+  spec.add_dependency "active-fedora", "~> 7.0"
   spec.add_development_dependency "bundler", "~> 1.6"
   spec.add_development_dependency "rake"
   spec.add_development_dependency "rspec"

data/lib/hydra/validations.rb

@@ -1,15 +1,16 @@
+require "active_model"
 require "hydra/validations/version"
-require "hydra/validations/helper_methods"
 
 module Hydra
   module Validations
     extend ActiveSupport::Concern
 
     included do
+      extend HelperMethods
       include HelperMethods
     end
 
   end
 end
 
-Dir[File.dirname(__FILE__) + "/validations/*validator.rb"].each { |file| require file }
+Dir[File.dirname(__FILE__) + "/validations/*.rb"].each { |file| require file }

data/lib/hydra/validations/single_cardinality_validator.rb

@@ -1,14 +1,26 @@
 #
 # SingleCardinalityValidator - validates that an enumerator value has size 0 or 1
 #
-#    validates :myattr, single_cardinality: true
+#    validates :my_attr, single_cardinality: true
+#    validates_single_cardinality_of :my_attr
 #
-class SingleCardinalityValidator < ActiveModel::EachValidator
+module Hydra
+  module Validations
 
-  def validate_each(record, attribute, value)
-    if value.respond_to?(:each)
-      record.errors.add(attribute, "can't have more than one value") if value.size > 1
+    class SingleCardinalityValidator < ActiveModel::EachValidator
+      def validate_each(record, attribute, value)
+        if value.respond_to?(:each)
+          record.errors.add(attribute, "can't have more than one value") if value.size > 1
+        end
+      end
+    end
+
+    module HelperMethods
+      def validates_single_cardinality_of *attr_names
+        validates_with SingleCardinalityValidator, _merge_attributes(attr_names)
+      end
     end
-  end
 
+  end
 end
+

data/lib/hydra/validations/uniqueness_validator.rb

@@ -0,0 +1,51 @@
+module Hydra
+  module Validations
+    #
+    # UniquenessValidator - an ActiveFedora model validator
+    #
+    # Usage:
+    #
+    #   validates :field, uniqueness: { solr_name: "field_ssim" }
+    #   validates_uniqueness_of :field, solr_name: "field_ssim"
+    #
+    # Restrictions:
+    #
+    # - Accepts only one attribute (can have more than one UniquenessValidator on a model, however)
+    # - Attribute cannot be multi-valued (:multiple=>true option of `has_attributes')
+    # - :solr_name option must be present
+    #
+    # CAVEAT: The determination of uniqueness depends on a Solr query.
+    # False negatives (record invalid) may result if, for example,
+    # querying a Solr field of type "text".
+    #
+    class UniquenessValidator < ActiveModel::EachValidator
+
+      def initialize(options = {})
+        super
+        attributes.each do |attr|
+          raise ArgumentError, "Cannot validate uniqueness on a multi-valued attribute: #{attribute}." if options[:class].multiple?(attr)
+        end
+      end
+
+      def check_validity!
+        raise ArgumentError, "UniquenessValidator accepts only a single attribute: #{attribues}" if attributes.length > 1 
+        raise ArgumentError, "UniquenessValidator requires the :solr_name option be present." unless options[:solr_name].present?
+      end
+
+      def validate_each(record, attribute, value)
+        conditions = {options[:solr_name] => value}
+        conditions.merge!("-id" => record.id) if record.persisted?
+        if record.class.exists? conditions
+          record.errors.add attribute, "has already been taken" 
+        end
+      end
+
+    end
+
+    module HelperMethods
+      def validates_uniqueness_of *attr_names
+        validates_with UniquenessValidator, _merge_attributes(attr_names)
+      end
+    end
+  end
+end

data/lib/hydra/validations/version.rb

@@ -1,5 +1,5 @@
 module Hydra
   module Validations
-    VERSION = "0.0.1"
+    VERSION = "0.1.0"
   end
 end

data/spec/spec_helper.rb

@@ -1,7 +1,4 @@
-$LOAD_PATH.unshift(File.expand_path('../../app/validators', __FILE__))
-
 require 'active_model'
-require 'active_support'
 require 'hydra/validations'
 
 RSpec.configure do |config|
@@ -25,7 +22,7 @@ RSpec.configure do |config|
   # Print the 10 slowest examples and example groups at the
   # end of the spec run, to help surface which specs are running
   # particularly slow.
-  config.profile_examples = 10
+  # config.profile_examples = 10
 
   # Run specs in random order to surface order dependencies. If you find an
   # order dependency and want to debug it, you can fix the order by providing

data/spec/validators/single_cardinality_validator_spec.rb

@@ -25,7 +25,7 @@ shared_examples "it validates the single cardinality of the field" do
   end
 end
 
-describe SingleCardinalityValidator do
+describe Hydra::Validations::SingleCardinalityValidator do
   before(:all) do
     class Validatable
       include ActiveModel::Validations
@@ -34,6 +34,7 @@ describe SingleCardinalityValidator do
     end
   end
   before(:each) { Validatable.clear_validators! }
+  after(:all) { Object.send(:remove_const, :Validatable) }
   subject { Validatable.new }
   describe ".validates" do
     before { Validatable.validates :field, single_cardinality: true }

data/spec/validators/uniqueness_validator_spec.rb

@@ -0,0 +1,66 @@
+require 'spec_helper'
+require 'active_fedora'
+
+shared_examples "it validates the uniqueness of the attribute value" do
+  context "when the value is not taken" do
+    before { allow(Validatable).to receive(:exists?).with(conditions) { false } }
+    it "should be valid" do
+      expect(subject).to be_valid
+    end
+  end
+  context "when the value is taken" do
+    before { allow(Validatable).to receive(:exists?).with(conditions) { true } }
+    it "should not be valid" do
+      expect(subject).not_to be_valid
+    end
+  end
+end
+
+describe Hydra::Validations::UniquenessValidator do
+
+  before(:all) do
+    class Validatable < ActiveFedora::Base
+      include Hydra::Validations
+      has_metadata name: 'descMetadata', type: ActiveFedora::QualifiedDublinCoreDatastream
+      has_attributes :title, datastream: 'descMetadata', multiple: false
+      has_attributes :creator, datastream: 'descMetadata', multiple: false
+      has_attributes :subject, datastream: 'descMetadata', multiple: true
+    end
+  end
+
+  after(:all) { Object.send(:remove_const, :Validatable) }
+
+  describe "exceptions" do
+    before { Validatable.clear_validators! }
+    it "cannot be used on a multi-valued attribute" do
+      expect { Validatable.validates :subject, uniqueness: { solr_name: "subject_ssim" } }.to raise_error
+    end
+    it "cannot be used on more than one attribute at a time" do
+      expect { Validatable.validates :title, :creator, uniqueness: { solr_name: "snafu_ssim" } }.to raise_error
+    end
+    it "cannot be used without the :solr_name option" do
+      expect { Validatable.validates :title, uniqueness: true }.to raise_error
+    end
+  end
+
+  describe "validation" do
+    subject { Validatable.new(pid: "foobar:1", title: "I am Unique!") }
+    let(:solr_name) { "title_ssi" }
+    before do
+      Validatable.clear_validators!
+      Validatable.validates_uniqueness_of :title, solr_name: solr_name
+    end
+    context "when the record is new" do
+      before { allow(subject).to receive(:persisted?) { false } }
+      it_behaves_like "it validates the uniqueness of the attribute value" do
+        let(:conditions) { {solr_name => subject.title} }
+      end
+    end
+    context "when the record is persisted" do
+      before { allow(subject).to receive(:persisted?) { true } }
+      it_behaves_like "it validates the uniqueness of the attribute value" do
+        let(:conditions) { {solr_name => subject.title, "-id" => subject.pid} }
+      end
+    end
+  end
+end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: hydra-validations
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.1.0
 platform: ruby
 authors:
 - dchandekstark
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-08-15 00:00:00.000000000 Z
+date: 2014-08-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activemodel
@@ -24,6 +24,20 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '4.0'
+- !ruby/object:Gem::Dependency
+  name: active-fedora
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '7.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '7.0'
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
@@ -74,17 +88,22 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".gitignore"
+- ".rspec"
+- ".travis.yml"
+- CONTRIBUTING.md
+- CONTRIBUTORS.md
 - Gemfile
 - LICENSE
 - README.md
 - Rakefile
 - hydra-validations.gemspec
 - lib/hydra/validations.rb
-- lib/hydra/validations/helper_methods.rb
 - lib/hydra/validations/single_cardinality_validator.rb
+- lib/hydra/validations/uniqueness_validator.rb
 - lib/hydra/validations/version.rb
 - spec/spec_helper.rb
 - spec/validators/single_cardinality_validator_spec.rb
+- spec/validators/uniqueness_validator_spec.rb
 homepage: https://github.com/duke-libraries/hydra-validations
 licenses:
 - APACHE2
@@ -98,7 +117,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '0'
+      version: 1.9.3
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
@@ -113,3 +132,4 @@ summary: Validations for Hydra applications, based on ActiveModel::Validations
 test_files:
 - spec/spec_helper.rb
 - spec/validators/single_cardinality_validator_spec.rb
+- spec/validators/uniqueness_validator_spec.rb

data/lib/hydra/validations/helper_methods.rb

@@ -1,14 +0,0 @@
-module Hydra
-  module Validations
-    module HelperMethods
-      extend ActiveSupport::Concern
-
-      module ClassMethods
-        def validates_single_cardinality_of *attr_names
-          validates_with SingleCardinalityValidator, _merge_attributes(attr_names)
-        end
-      end
-
-    end
-  end
-end