feat(rdm.migration): Configurable auto-adding secondary community

[sakshamarora1]

closes: #542

https://codimd.web.cern.ch/g3bn8n7LRimDeil-TDDIlA

[kpsherva]

to add: 'publication-conferencenote', added recently

[kpsherva]

are you sure that this covers everything? I would also check if the output json in access.files has it set to restricted or not

[sakshamarora1]

I tested all the possible scenarios in the test cases. Could you also check that and let me know if something is missing?

There is no access.files populated in this flow. Do you mean here? It only sets enabled key

cds-migrator-kit/cds_migrator_kit/rdm/records/transform/transform.py

Lines 781 to 785 in 059313b

	record_json_output = {
	"files": self._files(record_dump),
	"pids": self._pids(json_data),
	"metadata": self._metadata(json_data, entry),
	}

cds-migrator-kit/cds_migrator_kit/rdm/records/transform/transform.py

Lines 240 to 244 in 059313b

	def _files(self, record_dump):
	"""Transform the files of a record."""
	record_dump.prepare_files()
	files = record_dump.files
	return {"enabled": bool(files)}

[kpsherva]

thanks for checking this. One more case comes to mind: we can set the whole collection to restricted, in this case we shouldn't add the scientific community either

[sakshamarora1]

It's the 2nd last test case: https://github.com/CERNDocumentServer/cds-migrator-kit/pull/544/files#diff-5a1d09172d5904b1883bd8a98ce9fcfbcd19b6d1042d8444b5340cfff638545eR149-R152