I apologize if this is a duplicate. I'm trying to document the new Components feature, but I'm running into problems when using UseControlNumber. In Bug 30327, the test plan mentions that UseControlNumber can be used or not, but from what I can see, ShowComponentRecords does not work with UseControlNumber. To test: 1. Enable ShowComponentRecords 1.1. Go to Administration > Global system preferences 1.2. Search for ShowComponentRecords 1.3. Choose either staff interface or both 1.4. Save 2. Enable UseControlNumber 2.1. Go to Administration > Global system preferences 2.2. Search for UseControlNumber 2.3. Choose 'Use' 2.4. Save 3. Add 773 $t and $w in the default MARC bibliographic framework 3.1. Go to Administration > MARC bibliographic framework 3.2. Click Actions > MARC structure next to Default framework 3.3. Search for 773 3.4. Click Actions > Edit subfields 3.5. Click on tab 't' 3.6. Check 'Editor' in the 'Advanced constraints' section 3.7. Click on tab 'w' 3.8. Check 'Editor' in the 'Advanced constraints' section 4. Catalog a host record 4.1. Go to Cataloging 4.2. Click on 'New record' 4.3. Fill in the mandatory fields (000, 003, 005, 008, 040$c, 245$a (note this one down), 942$c) 4.4. Enter a number in 001 (and note it down) 4.5. Save (no need to create an item) 5. Catalog a child record 5.1. Go to Cataloging 5.2. Click on 'New record' 5.3. Fill in the mandatory fields (000, 003, 005, 008, 040$c, 245$a, 942$c) 5.4. Fill in 773$a with the title (245$a) of the host record 5.5. Fill in 773$w with the control number (001) of the host record 5.6. Save (no need to create an item) 6. If necessary, reindex 7. Go to the host record --> The child record doesn't appear 8. Change UseControlNumber back to Don't use (steps 2) --> The child record appears
Hi Caroline, same issue with Elasticsearch/Zebra?
(In reply to Katrin Fischer from comment #1) > Hi Caroline, same issue with Elasticsearch/Zebra? I did this with ES on my local installation and with Zebra on a BW sandbox.
Hi Caroline, do you still happen to know were you were testing? If it was an updated installation, the cnr index might have been missing as it's not added on update for Elasticsearch.