cocina-models 0.34.0 → 0.34.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 258bc916aaaff62a84cd0bd264f8957e3c916310134ef3372cfdd3eca4c1ff4e
-  data.tar.gz: c26a6cc519230a25d19b218ddcec52fa552ea7780f647b6d449aee223be35eef
+  metadata.gz: 47e0e5c391575050da0d7ec099da98ced48dc06f5d7ba2a2df5f53f3e687e04d
+  data.tar.gz: cc63b9adc18d069b325ddedf8c019529fa10655168a34e12aa0114220793d372
 SHA512:
-  metadata.gz: cd057f437502f2e54f6b2c689b6aef4c808ac4912c91d87755abfeb13c24100ef3380f262e7ec27f42592ecbd59b16d68669c878a31c55fc2402f069c5142f1e
-  data.tar.gz: 5a27ebb9108e9838117b02ec015bb025120d82e3f90749b12d23b523f3eea4efe865b6e405f649574f10f88ee0a70811334c339e9d522f5f1186b72f59df9240
+  metadata.gz: f2f94eb4be540092d833435fec055b48a43d8c3d8b67ffa746dca94607810b23bce102cb0d20fe6eb6097ba721f83be403b2498c881b2dbf448f2c0f2341a5f4
+  data.tar.gz: cbae9dff9f1f89bfc9e7557086f63a3dae4941eb4785ba29e2f006fde18a6bdc51a4d747ea74af7d0211e19e20c1f53f2d949d1b233e9f394b6abb6aaf1fae7f

data/lib/cocina/generator/generator.rb

@@ -17,10 +17,13 @@ module Cocina
       def generate
         clean_output
 
-        schemas.each_key do |schema_name|
+        # rubocop:disable Style/HashEachMethods
+        # This is not a Hash
+        schemas.keys.each do |schema_name|
           schema = schema_for(schema_name)
           generate_for(schema) if schema
         end
+        # rubocop:enable Style/HashEachMethods
 
         generate_vocab
       end

data/lib/cocina/models/identification.rb

@@ -3,6 +3,8 @@
 module Cocina
   module Models
     class Identification < Struct
+      # Unique identifier in some other system. This is because a large proportion of what is deposited in SDR, historically and currently, are representations of objects that are also represented in other systems. For example, digitized paper and A/V collections have physical manifestations, and those physical objects are managed in systems that have their own identifiers. Similarly, books have barcodes, archival materials have collection numbers and physical locations, etc. The sourceId allows determining if an item has been deposited before and where to look for the original item if you're looking at its SDR representation.
+
       # example: sul:PC0170_s3_Fiesta_Bowl_2012-01-02_210609_2026
       attribute :sourceId, Types::Strict::String.meta(omittable: true)
       attribute :catalogLinks, Types::Strict::Array.of(CatalogLink).meta(omittable: true)

data/lib/cocina/models/request_dro.rb

@@ -25,7 +25,7 @@ module Cocina
       attribute :type, Types::Strict::String.enum(*RequestDRO::TYPES)
       attribute :label, Types::Strict::String
       attribute :version, Types::Strict::Integer
-      attribute(:access, DROAccess.default { DROAccess.new })
+      attribute :access, DROAccess.optional.meta(omittable: true)
       attribute(:administrative, Administrative.default { Administrative.new })
       attribute :description, Description.optional.meta(omittable: true)
       attribute(:identification, RequestIdentification.default { RequestIdentification.new })

data/lib/cocina/models/request_identification.rb

@@ -3,6 +3,8 @@
 module Cocina
   module Models
     class RequestIdentification < Struct
+      # Unique identifier in some other system. This is because a large proportion of what is deposited in SDR, historically and currently, are representations of objects that are also represented in other systems. For example, digitized paper and A/V collections have physical manifestations, and those physical objects are managed in systems that have their own identifiers. Similarly, books have barcodes, archival materials have collection numbers and physical locations, etc. The sourceId allows determining if an item has been deposited before and where to look for the original item if you're looking at its SDR representation.
+
       # example: sul:PC0170_s3_Fiesta_Bowl_2012-01-02_210609_2026
       attribute :sourceId, Types::Strict::String
       attribute :catalogLinks, Types::Strict::Array.of(CatalogLink).meta(omittable: true)

data/lib/cocina/models/version.rb

@@ -2,6 +2,6 @@
 
 module Cocina
   module Models
-    VERSION = '0.34.0'
+    VERSION = '0.34.1'
   end
 end

data/openapi.yml

@@ -716,11 +716,11 @@ components:
         sourceId:
           type: string
           description: >
-            Unique identifier in some other system. This is because a large proportion of what is deposited in SDR, 
-            historically and currently, are representations of objects that are also represented in other systems. 
-            For example, digitized paper and A/V collections have physical manifestations, and those physical objects are managed 
-            in systems that have their own identifiers. Similarly, books have barcodes, archival materials have collection numbers 
-            and physical locations, etc. The sourceId allows determining if an item has been deposited before and where to 
+            Unique identifier in some other system. This is because a large proportion of what is deposited in SDR,
+            historically and currently, are representations of objects that are also represented in other systems.
+            For example, digitized paper and A/V collections have physical manifestations, and those physical objects are managed
+            in systems that have their own identifiers. Similarly, books have barcodes, archival materials have collection numbers
+            and physical locations, etc. The sourceId allows determining if an item has been deposited before and where to
             look for the original item if you're looking at its SDR representation.
           example: 'sul:PC0170_s3_Fiesta_Bowl_2012-01-02_210609_2026'
         catalogLinks:
@@ -879,7 +879,6 @@ components:
         geographic:
           $ref: '#/components/schemas/Geographic'
       required:
-        - access
         - administrative
         - identification
         - label
@@ -978,11 +977,11 @@ components:
         sourceId:
           type: string
           description: >
-            Unique identifier in some other system. This is because a large proportion of what is deposited in SDR, 
-            historically and currently, are representations of objects that are also represented in other systems. 
-            For example, digitized paper and A/V collections have physical manifestations, and those physical objects are managed 
-            in systems that have their own identifiers. Similarly, books have barcodes, archival materials have collection numbers 
-            and physical locations, etc. The sourceId allows determining if an item has been deposited before and where to 
+            Unique identifier in some other system. This is because a large proportion of what is deposited in SDR,
+            historically and currently, are representations of objects that are also represented in other systems.
+            For example, digitized paper and A/V collections have physical manifestations, and those physical objects are managed
+            in systems that have their own identifiers. Similarly, books have barcodes, archival materials have collection numbers
+            and physical locations, etc. The sourceId allows determining if an item has been deposited before and where to
             look for the original item if you're looking at its SDR representation.
           example: 'sul:PC0170_s3_Fiesta_Bowl_2012-01-02_210609_2026'
         catalogLinks:

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: cocina-models
 version: !ruby/object:Gem::Version
-  version: 0.34.0
+  version: 0.34.1
 platform: ruby
 authors:
 - Justin Coyne