cocina-models 0.84.1 → 0.84.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9e1b47286ce6d52c99a76f6370a1f1a902d204759a7e0d11966b42d94d01ee19
-  data.tar.gz: e6f5f432fab07a70965b78b94f3f5a1ff6e103ce274011ee55b7a130ae7bc974
+  metadata.gz: ec3a00a348ca9a851ee3455b7b0208628ca9590556ad76b0f536c4da3e1b6079
+  data.tar.gz: 156105d8055745c353db2690e2c39b72a043243272fddc72fb80e5e9a42b81c4
 SHA512:
-  metadata.gz: '0908f1699111ae772ebea61c0f5824c78cd694640aa3acaaded5311f2039a366469765206cf88f49410734054d660cbb6414afa0695c5a3b831b42be857e30ac'
-  data.tar.gz: 075d804c7525993965ffe30ae6d7e266c62d8a1b842cebc7096db3cd0c824af1b733180740faf3ba7db246cdd4c822ca9e67699cfa160810e62f12e0e919ea5d
+  metadata.gz: ff595ddde9a4729ed1e77239d78b7d1729798708bb44a407a6019d98943b50d8f14a3ad12fa06f17085294d499a32b82ece50f7ca6f23a30ce857bcd12a2de87
+  data.tar.gz: 3bdb368b93e0ba0fc8f865cbb2888045589c2169af810f3380f18e2c8511fafea30fc088980a4503f6f0405a1b60daf575c1df07ac7463830058e9517827d97a

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    cocina-models (0.84.1)
+    cocina-models (0.84.4)
       activesupport
       deprecation
       dry-struct (~> 1.0)

data/README.md

@@ -87,6 +87,38 @@ RAILS_ENV=production bin/validate-cocina -p 8
 ```
 5. Check `validate-cocina.csv` for validation errors.
 
+## Running Reports in DSA
+
+Custom reports stored in dor-services-app can be run similarly to validation testing described above.
+
+1. Go the sdr-infra box:
+
+```
+ssh deploy@sdr-infra
+```
+
+2. Go to the dor-services-app directory and reset to main if needed (verify nobody else is using this first though):
+
+```
+cd dor-services-app
+git status # see if there are any unsaved changes, if so, you may need to git stash them
+git pull # OR git reset --hard main   to just ditch any local unsaved changes
+```
+
+3. Connect to the desired database by setting the environment variables as described in the section above.  This must be done each time you SSH back into the box to run a new report.
+
+4. Run the report (good idea to do it in a screen or via background process in case you get disconnected):
+
+```
+bundle exec bin/rails r -e production "BadIso8601Dates.report" > BadIso8601Dates.csv
+```
+
+5. When done, you can pull the report to your laptop as needed:
+
+```
+scp deploy@sdr-infra:/opt/app/deploy/dor-services-app/BadIso8601Dates.csv BadIso8601Dates.csv
+```
+
 ## Releasing
 
 ### Step 0: Share intent to change the models

data/lib/cocina/models/validators/date_time_validator.rb

@@ -76,7 +76,8 @@ module Cocina
           #
           # So we catch the false positives from the upstream gem and allow
           # this pattern to validate
-          /\AY-?\d{5,}\Z/.match?(value)
+          /\AY-?\d{5,}\Z/.match?(value) ||
+            /\A-?\d{1,3}\Z/.match?(value) # temporarily allow format violations
         end
 
         def valid_iso8601?(value)
@@ -96,11 +97,9 @@ module Cocina
           # * YYYY
           # * YYYY-MM
           #
-          # So we catch the false positives from the upstream gem and allow
+          # This catches the false positives from the upstream gem and allow
           # these two patterns to validate
-          #
-          # Also have a temporary exemption for MM/DD/YY
-          %r{\A((\d{4}(-0[1-9]|-1[0-2])?)|(\d{2}/\d{2}/\d{2}))\Z}.match?(value)
+          /\A\d{4}(-0[1-9]|-1[0-2])?\Z/.match?(value)
         end
 
         def druid

data/lib/cocina/models/version.rb

@@ -2,6 +2,6 @@
 
 module Cocina
   module Models
-    VERSION = '0.84.1'
+    VERSION = '0.84.4'
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: cocina-models
 version: !ruby/object:Gem::Version
-  version: 0.84.1
+  version: 0.84.4
 platform: ruby
 authors:
 - Justin Coyne
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2022-08-25 00:00:00.000000000 Z
+date: 2022-09-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport