cocina-models 0.107.0 → 0.107.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5274bff6327cebe2e04f7cc145fde055203131ae9885b4f654ff83dbbbe57408
-  data.tar.gz: 2cf28892860fdf3eb011a54aaaf4f6a25663f85cf66b8a1b15280b4165fe52f3
+  metadata.gz: 3e982057b0f0017c03ce8809fa93494bd179b28a90e6ad3f32ad6859c4a8249c
+  data.tar.gz: 4777322f4d9b18fa6d814b36974dbbbd9e79857a4ce5149a756ae737e82ca49c
 SHA512:
-  metadata.gz: 46b42f34df5bf8aba16f2d47110f8d81ae5f1be62b0b5aeda6fba9898b911540788a6f9ff23318cc7e0870a6c57a8dc95a14b50ced333628ef6f703fd842872f
-  data.tar.gz: a769621283a3433cebb98fff0e3a872f21016050e38770932af0aafc1634993631d31e50bddc58cc0720c6002fcaa9ae48fac840aa6042f39d55a745c6a7ec0b
+  metadata.gz: c0c1136149b28c85dfa4c7a5e1aab4ee6829beecb2a04367db82a85f31a4a84aca774a3243fdbbfac34db1dca4d6f7624eaf399548db69a281c0e7059136d67a
+  data.tar.gz: 0ba5d2b587e122a0ab1cd363fcc5c32e0fc3a3a26ae35621967bcb8e0eead73bc87d86f263520be8b6d831ca528f2e7e0a85138f545e31ff8381d90bd826971c

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    cocina-models (0.107.0)
+    cocina-models (0.107.1)
       activesupport
       deprecation
       dry-struct (~> 1.0)
@@ -36,7 +36,7 @@ GEM
     attr_extras (7.1.0)
     base64 (0.3.0)
     benchmark (0.4.1)
-    bigdecimal (3.2.3)
+    bigdecimal (3.3.1)
     byebug (12.0.0)
     committee (5.0.0)
       json_schema (~> 0.14, >= 0.14.3)
@@ -78,7 +78,7 @@ GEM
     i18n (1.14.7)
       concurrent-ruby (~> 1.0)
     ice_nine (0.11.2)
-    json (2.15.0)
+    json (2.15.1)
     json_schema (0.21.0)
     jsonpath (1.1.5)
       multi_json
@@ -86,7 +86,7 @@ GEM
     lint_roller (1.1.0)
     logger (1.7.0)
     mini_portile2 (2.8.9)
-    minitest (5.25.5)
+    minitest (5.26.0)
     multi_json (1.17.0)
     nokogiri (1.18.10)
       mini_portile2 (~> 2.8.2)
@@ -99,9 +99,9 @@ GEM
       racc
     patience_diff (1.2.0)
       optimist (~> 3.0)
-    prism (1.5.1)
+    prism (1.6.0)
     racc (1.8.1)
-    rack (3.2.1)
+    rack (3.2.3)
     rainbow (3.1.1)
     rake (13.3.0)
     regexp_parser (2.11.3)
@@ -109,12 +109,12 @@ GEM
       rspec-core (~> 3.13.0)
       rspec-expectations (~> 3.13.0)
       rspec-mocks (~> 3.13.0)
-    rspec-core (3.13.5)
+    rspec-core (3.13.6)
       rspec-support (~> 3.13.0)
     rspec-expectations (3.13.5)
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.13.0)
-    rspec-mocks (3.13.5)
+    rspec-mocks (3.13.6)
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.13.0)
     rspec-support (3.13.6)
@@ -158,7 +158,7 @@ GEM
     unicode-display_width (3.2.0)
       unicode-emoji (~> 4.1)
     unicode-emoji (4.1.0)
-    uri (1.0.3)
+    uri (1.0.4)
     zeitwerk (2.7.3)
 
 PLATFORMS

data/README.md

@@ -91,32 +91,8 @@ RAILS_ENV=production bin/validate-cocina -p 8
 
 ## Running Reports in DSA
 
-Custom reports stored in dor-services-app can be run similarly to validation testing described above.
-
-1. Connect to the `sdr-infra` box:
-    ```shell
-    ssh sdr-infra
-    ```
-1. Start a shell as the `deploy` user:
-    ```shell
-    # you may or may not need to supply the `-n SUNETID` argument
-    ksu deploy
-    ```
-1. Go to the `~/dor-services-app` directory and reset to main if needed (verify nobody else is using this first though):
-    ```shell
-    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
-    ```
-1. 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.
-1. Run the report (good idea to do it in a screen or via background process in case you get disconnected):
-    ```shell
-    bundle exec bin/rails r -e production "BadIso8601Dates.report" > BadIso8601Dates.csv
-    ```
-1. When done, you can pull the report to your laptop as needed:
-    ```shell
-    scp sdr-infra:/opt/app/deploy/dor-services-app/BadIso8601Dates.csv .
-    ```
+See https://github.com/sul-dlss/dor-services-app/blob/main/README.md#running-reports
+
 
 ## Releasing a patch change
 A patch change is a change that (1) does not affect the data model; (2) does not alter the openapi.yml; and more broadly (3) does not matter if some applications have the change and others do not.
@@ -143,7 +119,7 @@ Send a note to `#dlss-infra-chg-mgmt` on Slack to let people know what is changi
 The release process is much like any other gem. While on main:
 1. Bump the version in `lib/cocina/models/version.rb`
 2. `bundle install` so that `Gemfile.lock` is updated.
-3. Commit those changes. 
+3. Commit those changes.
 4. Run:
 ```
 bundle exec rake release
@@ -179,11 +155,11 @@ Copy and paste the cocina-models schemas to each project's `openapi.yml`. By con
 If you updated the `openapi.yml` in step 3A, use the same PR for step 3B. Why? When [dor-services-app](https://github.com/sul-dlss/dor-services-app), for example, is updated to use the new models (via the auto-update script), these clients should be updated at the same time or there is risk of models produced by dor-services-app not being acceptable to the clients.
 
 1. Perform `bundle update --conservative cocina-models dor-services-client` in the  services above and make PRs for those repos if they don't already exist. You may first need to update how these gems are pinned in the `Gemfile` in order to bump them.
-2. Note that sdr-client is not currently used in these applications, but if it were, would also need to be bumped to the latest release. 
+2. Note that sdr-client is not currently used in these applications, but if it were, would also need to be bumped to the latest release.
 
 #### Step 3C: Merge 'em
 
-Get the directly coupled services PRs merged before the deploy in step 5. 
+Get the directly coupled services PRs merged before the deploy in step 5.
 
 See the IMPORTANT note above about the timing of merging these PRs if you are waiting for dependency updates to make the updates to other dependent applications.
 
@@ -211,7 +187,7 @@ Create a branch and update cocina-models:
 ```
 bundle update --conservative cocina-models
 ```
-Once merged, it will deploy to stage via CD. 
+Once merged, it will deploy to stage via CD.
 
 ### Step 5: Deploy and test
 
@@ -228,7 +204,7 @@ It is safest to ensure _all_ the integration tests run cleanly.  However, patch
 
 **[Turn off Google Books](https://sul-gbooks-prod.stanford.edu/features) when deploying to production.** This avoids failed deposit due to a temporary Cocina model mismatch. Unlike other applications, the deposits will fail without retry and require manual remediation.
 
-In addition to deploying infrastructure apps via sdr-deploy, tag and cut a release of purl-fetcher. That will trigger its deploy to production. 
+In addition to deploying infrastructure apps via sdr-deploy, tag and cut a release of purl-fetcher. That will trigger its deploy to production.
 
 ## Usage conventions
 

data/description_types.yml

@@ -99,6 +99,8 @@ contributor.note:
     description: Institution with which the contributor is associated.
   - value: citation status
     description: Indicator of whether the contributor should be included in the citation.
+  - value: contact email
+    description: Preferred email contact for contributor.
   - value: description
     description: Biographical information about the contributor.
 event:

data/docs/description_types.md

@@ -106,6 +106,8 @@ _Path: contributor.note.type_
     * Institution with which the contributor is associated.
   * citation status
     * Indicator of whether the contributor should be included in the citation.
+  * contact email
+    * Preferred email contact for contributor.
   * description
     * Biographical information about the contributor.
 # Event types

data/lib/cocina/models/mapping/to_mods/name_writer.rb

@@ -97,7 +97,7 @@ module Cocina
             if parallel_name_values.size == 1
               contrib_name_value_slice = Cocina::Models::Builders::NameTitleGroupBuilder.value_slices(parallel_name_values.first)
               name_title_group = name_title_vals_index[contrib_name_value_slice]&.values&.first
-              write_name_from_parallel(contributor, contributor.name.first, parallel_name_values, name_title_group, nil)
+              write_name_from_parallel(contributor, contributor.name.first, parallel_name_values.first, name_title_group, nil)
             elsif parallel_name_values.size == 2 && display_type_parallel_name
               contrib_name_value_slice = Cocina::Models::Builders::NameTitleGroupBuilder.value_slices(parallel_name_values.first)
               name_title_group = name_title_vals_index[contrib_name_value_slice]&.values&.first

data/lib/cocina/models/version.rb

@@ -2,6 +2,6 @@
 
 module Cocina
   module Models
-    VERSION = '0.107.0'
+    VERSION = '0.107.1'
   end
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: cocina-models
 version: !ruby/object:Gem::Version
-  version: 0.107.0
+  version: 0.107.1
 platform: ruby
 authors:
 - Justin Coyne
 bindir: exe
 cert_chain: []
-date: 1980-01-02 00:00:00.000000000 Z
+date: 2025-10-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -535,7 +535,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.7.0
+rubygems_version: 3.6.2
 specification_version: 4
 summary: Data models for the SDR
 test_files: []