-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Books: clean aleph numbers #15
Comments
@agentilb http://cds.cern.ch/record/611669/export/hm?ln=en contains 035$$CERCER but the number does not start with |
Hi @ludmilamarian , The 970 contains the Aleph number: 000611669 970__ $$a002371072CER, here it seems to match with 035a. So we can ignore this field. |
Hi @agentilb Unfortunately there is a bit of a grey zone. There are currently 13 records out of the ones we plan to migrate (71 records in total in CDS: see ticket #21 ) that have a 035 CERCER number that does not match the 970. Can you take a look and let me know how should I proceed with them?
|
787__w Based on the above 24records have been identified as needed to be updated and 1 needs manual update @agentilb
|
@ludmilamarian regarding those 13 records and the 58 mentioned in #21. I have checked a bit, and in some cases, the records are merged records or cloned records, that's explains the discrepancy between 035 and 970. |
770__w 2 records need to be fixed manually: @agentilb
|
@ludmilamarian |
772__w |
785__w To fix manually @agentilb
|
780__w To fix manually @agentilb
|
962__b
|
In principle, only 962__b starting with 00 should be converted (at least for the articles, books, proceedings and standards). In most cases, indeed, there is a $$n with a conference code. In this case, it is actually a good idea to check against the 111__g of the corresponding record, if it is not too complicated. Then for the records that have 962__lCER or CERCER, it concerns mostly multimedia and archive records. In this case, I have the feeling that even if there is no 00 in 962__b the number is an Aleph number. The number of cases here is small, so I can check those myself. For the 962__l where the value is 'ADMBUL', 'MMD' or 'PHOPHO', it concerns mostly pictures. We have to check if there are Aleph number in there. |
@agentilb indeed the |
@agentilb records with |
I have cleaned all the records with 962__l:'CER'. I.e. checking if the number was Aleph or CDS id, correcting when necessary, and deleting the 962__l. 962__l:PHOPHO-> it seems to correspond to records (mostly Bulletin articles) linked with photos. 962__l:MMD it seems to correspond to records (mostly Bulletin articles) linked with photos. 962__l:ADMBUL it seems to correspond to photo records linked with Bulletin issues (all are from the years 2000-2001). Those will be need to be modified at some point, but they are not part of the current migration. |
@agentilb |
Hi @ludmilamarian |
@agentilb indeed, I discovered this case with |
@agentilb looking at the |
Hi @ludmilamarian I fear this concerns one specific collection of books which was curated by one student in 2013, unfortunately, I don't think we can easily retrieve the 970/035. But this should concern less than 200 records, If I give you a selection of some 143 recids, is it easy to check the historical version before this Revision 2013-09-12 17:20:23 (I hope it was done in one time...) ? |
Hi @agentilb I fixed most of the linking, we are missing 1'895 links (so 1895 Aleph IDs still in 962__b) that have not been straightforward to fix. Out of these:
|
Hi @ludmilamarian, Thanks! I'll have a look to those lists, and let you know if something else can be done. |
@agentilb let me know how you wish to proceed, I would like to try to finish the task this week :-) |
Hi @ludmilamarian, I started to study those lists manually with an intern, and I think we will be able to handle them on our side. This should be done by the end of the week. So no further action is required from you, I guess :-) |
That is fantastic news @agentilb ! This means we are close to have this project finished! I will leave the ticket open until you confirm that everything is fixed. Also, there are just a few cases left for |
@ludmilamarian the 780 are now done. |
All Aleph numbers have now been cleaned in the 962__b. |
More or less 25,000 records need to be corrected.
One way to see if the value is an Aleph number is that the number stats with 000s:
https://cds.cern.ch/search?ln=en&sc=1&p=962__b%3A%22000*%22+or+785%3A%22000*%22+or+770%3A%22000*%22+or+780%3A%22000*%22+or+787%3A%22000*%22+or+772%3A%22000*%22&action_search=Search&op1=a&m1=a&p1=&f1=&c=Articles+%26+Preprints&c=Books+%26+Proceedings&c=Presentations+%26+Talks&c=Periodicals+%26+Progress+Reports&c=Multimedia+%26+Outreach
(The search is maybe not 100% accurate).
The fields that need to be checked are:
Additionally:
The matching needs to be done against 970__a where there is ‘CER’ and one needs to replace this value with the corresponding CDS record number.
Here is an example:
https://cds.cern.ch/record/1163043?ln=en
As far as as know, there is also the field 035 that contains Aleph Numbers when $$9CERCER:
Ex: https://cds.cern.ch/record/1220684?ln=en -> to be checked if it is still in use for something
( requires #21 )
The text was updated successfully, but these errors were encountered: