iCode is a stand alone coding tool. This means that it has an enormous amount of flexibility when it comes to data and records that can be added to the projects. Below are a few examples of different projects and their workflows.
Type
Included data (examples)
Description
iSearch project
Source Data:
iSearch (you choose the url)
Make a project from one iSearch url or several urls by copying and pasting that url in Manage Content: Add Content
You can add urls at different times if a project is being created from a number of different searches, or ad all urls at once if you have them available
Adding all urls at once alleviates the need to go through the set up with each url added
If making a project from several urls, you will need to make sure that the filters applied to each url are consistent to alleviate issues in data mismatches
You have the option to make this type of project dynamic to some extent. See Create a Project for more details.
Spreadsheet
Source data:
Downloaded iSearch Data
Make a project from a spreadsheet with your data using Manage Content: Add Records. Prior to uploading, clean the data to remove any unique formatting that may exist in the spreadsheet and review blank fields so they are being coded consistently. Note every record needs an ID. See example spreadsheet here.
Note any spreadsheet cannot be made dynamic in iCode
Spreadsheet
Source data:
RFI responses (single upload)
Make a project from a spreadsheet with your data using Manage Content: Add Records. Prior to uploading, clean the data to remove any unique formatting that may exist in the spreadsheet and review blank fields so they are being coded consistently. Note every record needs an ID. See example spreadsheet here.
Note any spreadsheet cannot be made dynamic in iCode
Spreadsheet
Source data:
Multiple uploads, i.e. RFI responses (rolling basis)
Make a project from an initial spreadsheet with some responses using Manage Content: Add Records. Subsequent uploads should be a continuous spreadsheet with all records and fields, or completely unique records only, ensuring that all previously uploaded fields exist for the new records for consistency. See use cases for multiple uploads of spreadsheets here.
iSearch project with custom fields
iSearch url with later additions in Upload Fields
Make a project from an iSearch url using Manage Content: Add Records. At any point after this, you can use the Upload fields button to upload a spreadsheet of System IDs and any appended/additional custom fields you want to add to the existing records in the project, i.e. Coder
Make a project from a spreadsheet with your data using Manage Content: Add Records. This would include the export from iSearch, with additional custom fields included in the spreadsheet.
This should be uploaded at one time, compared to the row above, where you would upload a spreadsheet with source iSearch data and then custom/additional fields. SeeManage Content versus Upload Fields tutorial.
Comments
0 comments
Article is closed for comments.