Feature update validation (#35)

* Update record validation to follow rules in https://www.loc.gov/marc/specifications/specrecstruc.html , including:

-  Validate that leader is 24 characters long (if configured with validationOption `leader: true`)
- Validate that leader contains only printable/graphic ASCII characters (if configured with validationOption `characters: true`)

- Validate that field tags are three characters long 
- Validate that field tags consist only of ASCII numeric characters (decimal integers 0-9) and/or ASCII alphabetic characters (uppercase or lowercase, but not both). (if configured with validationOption `characters: true`)
- Validate that controlField tags start with '00' or ASCII alphabetic characters (if configured with validationOption `characters: true`)
- Validate that dataField tags do not start with '00' (if configured with validationOption `characters: true`)

- Validate that controlFields do not have ind1, ind2 or subfields
- Validate that controlField values contain only printable/graphic ASCII characters (if configured with validationOption `characters: true`)
- Validate that controlField value does not exceed maximum length for a field

- Validate that dataFields do not have value

- Validate that indicators are one character long
- Validate that indicators consist only of blanks or ASCII numeric or lowercase alphabetic characters (if configured with validationOption `characters: true`)

- Validate that subfield codes are one character long
- Validate that subfield codes consist only of printable/graphic ASCII characters excluding blank (if configured with validationOption `characters: true`)

- Validate that subfield values do not contain ASCII control characters (if configured with validationOption `noControlCharacters: true`)
- Validate that subfield values do not exceed maximum length for a field

- Validate that fields or subfields do not have additional properties (if configured with validationOption `noAdditionalProperties: true`)

* Add new validationOption `strict: true` that causes all other validationOptions to be handled as `true`


* Add new validationOptions and update default validationOptions:
```
strict: false                  // If true, all validationOptions below are handled as if true

fields: true,                  // Do not allow record without fields
subfields: true,               // Do not allow empty subfields
subfieldValues: true,          // Do not allow subfields without value
controlFieldValues: true       // Do not allow controlFields without value
leader: false,                 // Do not allow record without leader, with empty leader or with leader with length != 24
characters: false              // Do not allow erronous characters in tags, indicators and subfield codes
noControlCharacters: false,    // Do not allow ASCII control characters in field/subfield values
noAdditionalProperties: false  // Do not allow additional properties in fields
```

* Update deps
* Update node-tests: v19.x -> v20.x

* Fix and add tests
* Add some debug
* Update and fix README
* Add commentary to schema

* 7.3.0-alpha.7

Author: ammsalme

.github/workflows/melinda-node-tests.yml

@@ -11,7 +11,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [16.x, 18.x, 19.x]
+        node-version: [16.x, 18.x, 20.x]
         # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
 
     steps:

README.md

@@ -17,7 +17,8 @@ const record = new MarcRecord();
 ```js
 const record = new MarcRecord(
   {
-    leader: 'foo',
+    leader: '02848ccm a22005894i 4500',
+',
     fields: [
       {tag: '001', value: 'foo'},
       {tag: '002', value: 'bar'},
@@ -35,17 +36,31 @@ const recordB = MarcRecord.clone(recordA)
 
 When constructing or modifying the record, validation checks are run. You may need to alter these checks to work with incomplete intermediate records.
 
+**strict**
+
+validationOption `strict: true` sets all the other validationOptions as true regardless of if they are defined
+validationOption `strict: false` sets other validationOptions as they are defined or as default
+
 **Global validation options:**
 
 ```js
 MarcRecord.getValidationOptions();
 
 // Default settings
+// These default validationOptions are (mostly) backwards compatible with marc-record-js < 7.3.0
+
 MarcRecord.setValidationOptions(
   {
-    fields: true,          // Do not allow record without fields
-    subfields: true,       // Do not allow empty subfields
-    subfieldsValues: true, // Do not allow subfields without value
+    fields: true,                  // Do not allow record without fields
+    subfields: true,               // Do not allow empty subfields
+    subfieldValues: true,          // Do not allow subfields without value
+    controlFieldValues: true,      // Do not allow controlFields without value
+    leader: false,                 // Do not allow record without leader, with empty leader or with leader with length != 24
+    characters: false,             // Do not allow erronous characters in tags, indicators and subfield codes
+    noControlCharacters: false,    // Do not allow ASCII control characters in field/subfield values
+    noAdditionalProperties: false, // Do not allow additional properties in fields
+
+    strict: false                  // If true, set all validationOptions to true
   }
 );
 ```
@@ -57,12 +72,20 @@ You can reset global validation options to default with empty object:
 MarcRecord.setValidationOptions({});
 ```
 
+You can set all global validation options to true with validationOption strict: true:
+
+```js
+// Set all validationOptions to true with strict: true
+MarcRecord.setValidationOptions({strict: true});
+```
+
+
 **Record specific validation options** can be given when constructing:
 
 ```js
 const record = new MarcRecord(
   {
-    leader: 'foo',
+    leader: '02848ccm a22005894i 4500',
     fields: []
   },
   {fields: false} // Allow empty fields
@@ -77,27 +100,27 @@ The following examples demonstrate the invalid records, when default validation
 // Error: fields[] is empty. Validation option: fields
 new MarcRecord(
   {
-    leader: 'foo',
+    leader: '02848ccm a22005894i 4500',
     fields: []
   }
 );
 
 // Error: subfields[] is empty. Validation option: subfields
 new MarcRecord(
   {
-    leader: 'foo',
+    leader: '02848ccm a22005894i 4500',
     fields: [
-      {tag: "021", subfields: []}
+      {tag: "509", , ind1: " ", ind2: " ", subfields: []}
     ]
   }
 );
 
 // Error: subfield has no value. Validation option: subfieldValues
 new MarcRecord(
   {
-    leader: 'foo',
+    leader: '02848ccm a22005894i 4500',
     fields: [
-      {tag: "021", subfields: [{code: "a", value: ""}]}
+      {tag: "509", ind1: " ", ind2: " ", subfields: [{code: "a", value: ""}]}
     ]
   }
 );
@@ -229,7 +252,7 @@ Failing examples:
 // Example record
 const record = new MarcRecord(
 {
-  leader: "foo",
+  leader: "02848ccm a22005894i 4500",
   fields: [
     {tag: "001", value: "bar"}
   ]
@@ -304,6 +327,6 @@ To serialize and unserialize MARC records, see [marc-record-serializers](https:/
 
 Copyright (c) 2014-2017 **Pasi Tuominen <[email protected]>**
 
-Copyright (c) 2018 **University Of Helsinki (The National Library Of Finland)**
+Copyright (c) 2018-2023 **University Of Helsinki (The National Library Of Finland)**
 
 This project's source code is licensed under the terms of **MIT License** or any later version.