curation request: LEP experiments and scientific committees

[kpsherva]

Hello everyone!

I've analysed another big chunk of data, and there are some inconsistencies, with which I need your help (instructions provided on the first spreadsheet):
https://docs.google.com/spreadsheets/d/1cQhyo9NuJUFIlRzwg7J98FFF_gA_bIaeEMNRHOeduGo/edit?gid=0#gid=0

please let me know once each sheet is addressed because it unblocks me to migrate it.

[PaulinaBaranowska]

Thanks @kpsherva
We will meet internally on Wednesday and split the work up between us.

[PaulinaBaranowska]

@kpsherva
We split up most of the errors between us and will start cleaning up.

We have a couple of questions though:

1. Error in 980__ "unknown resource type or indico resource type, can we assign correct resource type?"
   There are a few values that we want to check with you:
   Question a : SLINTNOTE can be found in the CDS Definitions https://cds.cern.ch/cdsdef.py but under the 'CDS Collection Indicators (980) attribution rules' part - are you sure it's not actually used?
   Question b: 'intnotecmspubl' is defined and used in "CMS Notes" and "CMS Conference Reports" collections. Why does it come up as undefined? Same for 'scicommpubllhcc'
   Question c: indico - I guess this is a value for records imported from indico? Can this be deleted or should it be moved to another field for reference?

2. Accelerator SLAC SLC not found.
   Is there a naming convention for non-CERN experiment values in 693? Or is it simply that the hyphen is missing?

Thanks for clarifying!

[PaulinaBaranowska]

@kpsherva
One more, sorry:
3. 269__ wrong date format:
What is the expected format? I believe it is DD MMM YYYY, but is just MMM YYYY or YYYY enough as well?
@SaraAlaouiVarea will be working on this

[FleurAH]

@kpsherva and @salomerohr
We have also another question regarding 852_a. Majority of those errors are linked to records with 852_a:CERNArchives.Bldg.61−S−001.
There are several issue regarding cleaning 852:

• Information contained in 852$a and 852$c has to be retained so that the documents can be located. Unlike the books, there is no other way to locate documents from the Archives yet.
• 852 is restricted information and has to be hidden from users.
• The Archivists are still working on those records as part of ongoing digitization projects.

I wonder if it could be possible to ignore records with 852:CERNArchives.Bldg.61−S−001 in the migration for the time being? Or do you think there is another solution here?

[kpsherva]

@kpsherva We split up most of the errors between us and will start cleaning up.

We have a couple of questions though:

1. Error in 980__ "unknown resource type or indico resource type, can we assign correct resource type?"
   There are a few values that we want to check with you:
   Question a : SLINTNOTE can be found in the CDS Definitions https://cds.cern.ch/cdsdef.py but under the 'CDS Collection Indicators (980) attribution rules' part - are you sure it's not actually used?

thanks for spotting this, it sliped out of my script configuration. I will map this to notes (we discussed this in the past). So nothing to do for SLINTNOTE

Question b: 'intnotecmspubl' is defined and used in "CMS Notes" and "CMS Conference Reports" collections. Why does it come up as undefined? Same for 'scicommpubllhcc'

CMS content shouldn't show up in the data set, I have a query which is too broad, because we don't want to migrate CMS yet, I will exclude this record from the set https://cds.cern.ch/record/687218/export/hm?ln=en

Question c: indico - I guess this is a value for records imported from indico? Can this be deleted or should it be moved to another field for reference?

I think I can assign a type automatically, I checked some records and it seems they are presentations when the type is indico, but what would reassure me I can do this, is if you check if this assumption is correct in each of these cases. Could you verify if I can assign presentations resource type if the 980 is indico?

2. Accelerator SLAC SLC not found.
   Is there a naming convention for non-CERN experiment values in 693? Or is it simply that the hyphen is missing?

the hyphen is missing, it needs curation - in case the value is missing from the new CDS, could you let us know that it should be added? I checked and SLAC-SLC is there but maybe we are missing other occurences

Thanks for clarifying!

thanks to you!

[kpsherva]

@kpsherva One more, sorry: 3. 269__ wrong date format: What is the expected format? I believe it is DD MMM YYYY, but is just MMM YYYY or YYYY enough as well? @SaraAlaouiVarea will be working on this

YYYY-MM-DD ideally, but other ones should be accepted too. The main problem is when the date is ambiguous, has a typo or is written in human readable way (plus in french) f.e. mai 2020

[kpsherva]

@kpsherva and @salomerohr We have also another question regarding 852_a. Majority of those errors are linked to records with 852_a:CERNArchives.Bldg.61−S−001. There are several issue regarding cleaning 852:

• Information contained in 852$a and 852$c has to be retained so that the documents can be located. Unlike the books, there is no other way to locate documents from the Archives yet.
• 852 is restricted information and has to be hidden from users.
• The Archivists are still working on those records as part of ongoing digitization projects.

I wonder if it could be possible to ignore records with 852:CERNArchives.Bldg.61−S−001 in the migration for the time being? Or do you think there is another solution here?

if you tell us, we can ignore specific values, yes
what I am concerned about is that we need to verify if some of the records were not synced to CLC and the information about location of the items will be lost - because we don't migrate the 852 to repository.cern - as it should be in CLC

for the items which should be in CLC and are not, I would suggest to create a CLC entry, and then mark the legacy record on CDS with ILSSYNC/ILSLINK so that I can be sure we verified the items and the location information is preserved on CLC - and I can safely drop it during migration