Hi Morgan , Irit and Paul ,

We found that the following 2 UIN numbers you have entered.

1 ) IC/0192/21a
2) IC/0192/21b

Due to the character behind UIN number (/a and /b), The Query is not able to find next max number to generate UIN number automatically. As we are generating max + 1 number.

Ex. UIN IC/0192/21 then next number will be generated IC/0192/02. But due to that character system throw error while going to + 1 in alphabeted character.

Can we allow to add UIN number manually ? Currently, In Dispute Document, The UIN textbox is disable. It mean you can not allow to enter UIN number manually.

Please suggest what we do ?

Hi Harsh ,

When you suggest entering the UIN number manually, how is that done, because Irit wasn't able to enter it manually above?

Thanks,

Morgan

Hi Morgan ,

Currently, The UIN textbox is disable. It mean admin user can not add UIN number manually. As due to getting alphabeted character the query is throwing error to increase max UIN + 1 number.

We will discuss more on tomorrow's call.

Ok. Sounds good, Harsh . I'll add it to the agenda.

Morgan

Hi Paul and Nafiseh ,
 
Could you please confirm that we have updated our processes, and that we've eliminated the user of alphabetical characters from UINs going forward.

Thanks,

Morgan

Yes, Morgan . We are not using any alphabetic characters in our UINs anymore.

Hi Morgan ,
we'll not use alphabetical characters in UINs going forward. As for the existing ones, Irit   has identified existing UIN with letters, and is working on them (deleting the ones with alphabetical characters and assigning new UINs to them). I think she's almost done, so let's wait for Irit to confirm. There are 3 disputes (UN/0003A, UN/0003B & UN/0003C) with alphabetical characters in them. We discussed this with Paul . As it is too remote that there will be any documents released under these UINs, we are going to leave them (including documents under these 3 UINs ) as is.

Thanks,

Nafiseh

Ok. Sounds good, Nafiseh ​ and Paul ​. I'll make this to-do complete then.

Thanks,

Morgan

Hi Morgan Paul Nafiseh  

Yes, this task was complete yesterday.  UINs with letters have been assigned new UINs.

Thank you,

Irit

Ok. Great. Thanks Irit ​.

Did we modify dispute UINs? I'm concerned what impact this will have on Legal Analytics?

Morgan

Hi Morgan :

Legal analytics analysis for UN/0003A, UN/0003B and UN/0003C are all done under UN/0003, so we shouldn't have any problem.

Thanks,

Paul

OK. Sounds good. What about the Article Citator Master List data? Is all the data related to disputes updated there as well, because this will be used to repopulate the application during the migration?

Thanks,

Morgan

Based on the UIN master list, no documents under UN/0003A, UN/0003B and UN/0003C have been coded; it seems like those documents were all simply uploaded without any analysis. Citator master lists also don't have any data recorded. As far as I could tell, all the data is entered under UN/0003. 

There were no SN entries under  UN/0003A, UN/0003B and UN/0003C.

Irit , could you confirm that there are no citator entries for any documents that had UINs under UN/0003A, UN/0003B and UN/0003C?

Thanks,

Paul

Paul Morgan  

There are no citator entries for any documents with UIN:  
UN/0003A, UN/0003B and UN/0003C

Thank you,
Irit

Paul Morgan  

I think I may have spoken too soon.  I will confirm. 

Hi  Paul Morgan  

I have confirmed - there are no citator entries for any documents with UIN:  
UN/0003A, UN/0003B and UN/0003C

Thank you,
Irit

Alright. Looks like we're in the clear. Onwards!

Morgan