ISLG Data Migration Map
The following is the spreadsheet mapping the data fields for the new ISLG: https://docs.google.com/spreadsheets/d/1Ho_yBR8gfCIqivmvkPy_hISkDGozdWsXxn46ImeQ-V4/edit#gid=0
The spreadsheet has two tabs. The Fields tabs provides descriptions of the meta fields applicable to each master list of the new application. Each master list includes a URL for the applicable wireframe:
Each master list has 8 or 11 columns that provide the following information:
Field Label: indicates the relevant field label assigned to the field.
Field Set (Dispute and Dispute Documents sections only): indicates if a field is included in a field set. If not Field Set is assigned, then field appears as first level fields (for more detail on field sets see: https://industrialagency.tpondemand.com/RestUI/Board.aspx#page=board/5389754907359543952&appConfig=eyJhY2lkIjoiRUM0QzUwNTU4QzZBNUQ1NjQxRkNGNUQyM0FFRDQxM0YifQ==&boardPopup=userstory/7985/silent)
Field Type: indicates the type of field.
Field Options: indicates the options available for the field.
Field Required: indicates whether an admin user is required to enter data for the field.
For details on field settings see:
https://industrialagency.tpondemand.com/RestUI/Board.aspx#page=board/5389754907359543952&appConfig=eyJhY2lkIjoiRUM0QzUwNTU4QzZBNUQ1NjQxRkNGNUQyM0FFRDQxM0YifQ==&boardPopup=userstory/7814/silent
Dependent Fields: indicates if there are any fields that are dependent on the current field.
Source of data for field upload: indicates where to source existing data to populate new application during initial migration and upload process. "N/A" indicates that there is no existing data for that field, and the data will be manually populated after the initial migration and upload process.
Sources for data include:
The spreadsheet has two tabs. The Fields tabs provides descriptions of the meta fields applicable to each master list of the new application. Each master list includes a URL for the applicable wireframe:
Each master list has 8 or 11 columns that provide the following information:
Field Label: indicates the relevant field label assigned to the field.
Field Set (Dispute and Dispute Documents sections only): indicates if a field is included in a field set. If not Field Set is assigned, then field appears as first level fields (for more detail on field sets see: https://industrialagency.tpondemand.com/RestUI/Board.aspx#page=board/5389754907359543952&appConfig=eyJhY2lkIjoiRUM0QzUwNTU4QzZBNUQ1NjQxRkNGNUQyM0FFRDQxM0YifQ==&boardPopup=userstory/7985/silent)
Field Type: indicates the type of field.
Field Options: indicates the options available for the field.
Field Required: indicates whether an admin user is required to enter data for the field.
For details on field settings see:
https://industrialagency.tpondemand.com/RestUI/Board.aspx#page=board/5389754907359543952&appConfig=eyJhY2lkIjoiRUM0QzUwNTU4QzZBNUQ1NjQxRkNGNUQyM0FFRDQxM0YifQ==&boardPopup=userstory/7814/silent
Dependent Fields: indicates if there are any fields that are dependent on the current field.
Source of data for field upload: indicates where to source existing data to populate new application during initial migration and upload process. "N/A" indicates that there is no existing data for that field, and the data will be manually populated after the initial migration and upload process.
Sources for data include:
- Existing ISLG (see Existing ISLG field for data sync below)
- UIN Master List (latest version): https://islg.egnyte.com/fl/TviHeAyF1p
- ISLG - Article Citator Master: https://islg.egnyte.com/fl/sbV4cIqc5z
- ISLG - Publication Citator Master: https://islg.egnyte.com/fl/sbV4cIqc5z
Existing ISLG field for data sync: indicates the relevant field(s) within the existing ISLG application that need to be synced with new applicable field in the new applications. "N/A" indicates that data does not need to be synced with the old application.
URLs & Screenshot: for "Source of data for field upload" and "Existing ISLG field for data sync", URLs are provided where applicable, including locations within existing ISLG application and screenshots providing further details.
Note about Fields: provides additional comments and details about how it should function.
The Dropdown Options tab provides the defined lists that will be used to populate options available for certain fields in the Fields tab. The applicable field is indicated by [Section]: [Field]:
Citator and Subject Navigator Data Map:
The map for migrating all documents and data from the existing to new ISLG application relevant to the citators and subject navigator.
The map is contained in the following tabs of the ISLG Data Migration Map: Dispute Documents, Arbitration Rules, Treaties and Subject Navigator
Each tab provides information on the relevant data and documents for the existing and new applications.
Fields and documents relevant to the existing application are on the left:
and the corresponding fields and documents relevant to the new application are on the right:
Documents and fields in the same row should be migrated from the existing to new applications:
Documents and fields are described with the following information:
URLs & Screenshot: for "Source of data for field upload" and "Existing ISLG field for data sync", URLs are provided where applicable, including locations within existing ISLG application and screenshots providing further details.
Note about Fields: provides additional comments and details about how it should function.
The Dropdown Options tab provides the defined lists that will be used to populate options available for certain fields in the Fields tab. The applicable field is indicated by [Section]: [Field]:
Citator and Subject Navigator Data Map:
The map for migrating all documents and data from the existing to new ISLG application relevant to the citators and subject navigator.
The map is contained in the following tabs of the ISLG Data Migration Map: Dispute Documents, Arbitration Rules, Treaties and Subject Navigator
Each tab provides information on the relevant data and documents for the existing and new applications.
Fields and documents relevant to the existing application are on the left:
and the corresponding fields and documents relevant to the new application are on the right:
Documents and fields in the same row should be migrated from the existing to new applications:
Documents and fields are described with the following information:
- Field/source label: label of field in application
- URL: URL location within application
- Screenshot(s): screenshot of page in application
- Comments: additional descriptions to give context to field or document
I've added the document above to provide more context to the ISLG Meta Data Fields Map spreadsheet. I haven't completed adding all the applicable changes to the spreadsheet (should have it finished later this week).
However,
Thanks,
Morgan
Thanks for providing above details.
Could you please specify the meaning of (Column D), (Column F) and Column (G) in source of existing data in spread sheet ?
We have found the ColumnD, F and G in UIN Master Spread sheet. Now, No need to explain.
Morgan
I still have a fair bit of work to do on the ISLG Meta Data Field Map. However, we should discuss an issue tomorrow concerning the fields I've added under the People section:
The highlighted fields above were added to incorporate data from the ISLG - Article Citator Master list that creates relationships between People, Organizations and Disputes, which will form the basic data for Legal Analytics. There are still many data fields to add to the other sections of the spreadhsheet, but I want to confirm that I'm on the right track. Please give this a review, and we'll discuss it more during tomorrow's call.
Thanks,
Morgan
I've completed adding all the details for mapping the data for everything excepts the Citators, Subject Navigator and Terms & Phrases (these will require some more detailed analysis). Essentially this should cover everything under Master Lists:
Thanks,
Morgan
I have gone through and completed updating the Meta Data Field Map spreadsheet. However, I noticed some issue we may need to address concerning the Citator and Navigator uploading tools.
Thanks,
Morgan
Further to our call this morning, I have made adjustments to the Dispute and Dispute Document sections of the ISLG Meta Data Fields Map to incorporate dispute UINs. Note that I have made the Dispute Document: UIN dependent on what dispute is associated with the Dispute Document, and includes requirements in the notes outlining how text in the field is automatically generated based on the associated dispute and other dispute documents already associated with that dispute.
Thanks,
Morgan
I have updated the ISLG Meta Data Field Map above. I've added columns to specify the settings for each field including type, options and required. I've also rearranged the columns so that they read left-to-right, and updated the descriptions above.
I've added all the settings for the fields under Dispute. Could you please review these and make sure it makes sense, and then I'll start filling in the other field types.
Thanks,
Morgan
That all makes sense to me. The only other recommendation I have is to clearly state which fields are included in a Field Set. Since you already have Tribunal and Annulment Committee fields grouped, I suggest adding the field set label (ie: in cell A18 add Field Set: Tribunal)
Mel
Right. I'll make a separate column for this and that data there.
Morgan
As I went through these again, I realized that there is issue with some fields where we're pulling data from another Master List. What happens when the admin user needs to create a new entries for another Master List? For example. when filling in the Counsel field for a dispute entry, the user will need to add new counsel to the People Master List.
I would expect that the admin user would have the ability to enter all the relevant data for the new People entry directly, without having to exit the Dispute entry page, but I don't think we have requirements that allow us to do that yet. How do you recommend we deal with this issue?
Morgan
Just following up on my comment above. I'm starting to rework the Meta Field Map quite substantially, and I just wanted to make sure you approve of my approach before I go too far down the road on this. Let me know your thoughts.
Thanks,
Morgan
You're right, based on our revised requirements around dynamic and required fields, we will have to adjust how we were planning on doing this.
I don't think this should affect the work you are doing for the data field mapping. We can capture the necessary requirements separately.
My current thought is that if an admin is inputting data into a field and needs to create a new entry they will have an option to 'create new'. The most consistent approach at this time will be to display the required fields for the new entry within a dialogue/pop-up. Only the required and dynamic fields would be within the dialogue with an option to open the full form in a new window. Once the admin saves, the entry would be added to the related master list.
Mel
I'll continue working through the Meta Field Map and get things completed on that end, and then we can work on getting things integrated into the wireframes and applicable cards on TargetProcess.
Also, as I mentioned in another message, we should probably have a call next week to discuss the design for admin side of legal analytics.
Morgan
I've finished updating the ISLG Meta Data Field Map. Everything has been updated with the new columns (field type, set, options and required) where applicable. I've also added the fields relevant to the dialogue/pop-ups we discussed above.
Thanks,
Morgan
In preparation for the data migration and upload process for the new ISLG application, I have made changes to the ISLG Meta Data Field Map spreadsheet: https://docs.google.com/spreadsheets/d/1Ho_yBR8gfCIqivmvkPy_hISkDGozdWsXxn46ImeQ-V4/edit#gid=0. I have modified and added the columns concerning source data and syncing with the existing application:
The purpose of these changes is to provide more detailed descriptions on the source data for the initial data upload and migration process, and specify which data needs to be synced back with the existing/old application. I have also included URLs that provide details on the locations of data within the existing ISLG application and screenshots with descriptions. Updated descriptions for "Source of data for field upload" and "Existing ISLG field for data sync" have been updated above as well:
Let me know if you have any questions or concerns. Otherwise, I will continue to review and update each master list over the next week.
Thanks,
Morgan
As we discussed this morning, please review the changes I have made to the ISLG Data Field Map above concerning the sourcing and syncing of data between the old and new applications, and let me know if any changes are needed in the way instructions are being provided.
Thanks,
Morgan
Here is a recording of our call this morning:
Thanks,
Morgan
I have completed mapping the documents and data relevant to second phase of the migration (i.e., documents and data relevant to the citators and subject navigator). The ISLG Data Migration Map and description above have been updated accordingly. Please review the Citator and Subject Navigator Data Map section in the description above for details on the additional mapping.
Note that I have not included any mapping details about migrating existing user data. Let me know if I need to add this to the map as well.
Please review and then we'll discuss next steps during my call with
Thanks,
Morgan
In preparation for tomorrow's call, I've added an additional tab to the ISLG Date Migration Map: User Data, which maps all applicable user data that will need to by migrated and synced between the existing and new applications:
Note we should discuss how we're going to synchronize data between the existing and old applications during the beta period. Ideally, we would want data from both applications to be tracked within the new application. Assuming this is possible, we'll want to add a column to the Group and User tracking tables that indicates whether a session was on the existing or new application.
Thanks,
Morgan