To assist users with the final transition, any remaining portfolios in iSearch 2.7 and the RFI tool will be migrated to iCode as projects. During the September–November transition period, Managers and Super Curators can also choose to migrate their portfolios to iCode.
The following sections describe important differences to keep in mind when reviewing migrated projects in iCode:
-
Viewable fields
- For migrated iSearch portfolios, only major table fields will be displayed by default in the new iCode project. To include additional fields, go to Manage Content and adjust the fields included in the project. You can also look up the System ID in iSearch 3.0 to view additional information. To change which included fields are displayed in iCode, use Modify View.
-
Record differences
- The number of records may differ because stale (previously deleted) records from iSearch/QVR will not be included in the new iCode project.
- Masked (hidden) records will not be retained in iCode projects.
- Records from the global grants database will not be included in migrated projects because iSearch 3.0 does not contain this database.
- L (Loan Repayment) grant records will not be retained in the iCode project because iSearch 3.0 does not contain these mechanisms.
-
Portfolio creation and automatic updates
-
Static iSearch portfolios will be migrated based on the records in the portfolio, not the search query originally used to create it.
- Record IDs will be copied to the new iCode project, and the corresponding fields and metrics will reflect their values on the migration date. For example, an RCR associated with a PMID will reflect the RCR value on the date of migration and will remain unchanged unless the project is made Dynamic.
- To allow metrics and other fields associated with those records to update, enable Dynamic in the migrated project. The same approach can be used for new iCode projects created from a set of IDs.
-
Dynamic iSearch portfolios will be migrated based on the search query used to create the portfolio. As a result, the migrated iCode project may contain more records than were present when the portfolio was last reviewed in iSearch.
- The original search or query is planned to be made available in iCode as a future feature. If you have questions or encounter issues, contact OPA for assistance. See the FAQ on expected differences in redirected searches for more information.
- RFI portfolios will be converted to spreadsheets and uploaded to iCode as projects. Coding fields will be retained. Attached files may not be migrated, although the file names should remain available. Highlighting will also be retained; however, because of how RFI data is transferred, you will need to reselect the fields in which the highlighting should be applied.
-
Static iSearch portfolios will be migrated based on the records in the portfolio, not the search query originally used to create it.
-
Data/Field settings
- Field settings are configured during migration, but you may need to make adjustments in Manage Content based on how you plan to use the data. For example, Appl ID is set as a Number by default, which works well when exporting data to Excel. However, in Search Assist, a numeric field will appear as a range. If you plan to use Appl ID in Search Assist, consider changing the field type to Short Text so you can select individual Appl IDs.
- For migrated RFI portfolios, the original ID will be stored in the Document ID field in the iCode project. This applies even if the project contains other ID fields. See What is a Document ID?
-
Vocabularies
- Vocabularies will be retained, but the process for using a previously created vocabulary is different in iCode. Because vocabularies are managed separately for each project, within your All Vocabularies tab, you may see multiple instances of the same vocabulary if it was reused across migrated projects. You can see which project each vocabulary belongs to and use the Name column filter to help locate a specific vocabulary. For more information, see the Coding Fields and Vocabularies article.
-
Highlighting
- Highlighting will also be retained. However, iCode provides a limited set of highlight colors, whereas the previous tools allowed users to select from a wider range of colors using a color wheel. Existing highlight colors will be matched to the closest available color in iCode. As a result, multiple existing colors may be mapped to the same color. If a close match is not available, the highlight will default to yellow. Note that in RFI style/uploaded spreadsheet projects, as mentioned above, because of how RFI data is transferred, you will need to reselect the fields in which the highlighting should be applied to view in the iCode project properly.
For more information about differences among previous versions of iSearch, see the iSearch 2.6/2.7 versus 3.0 features FAQ.
For migrated RFI portfolios, all originally uploaded information should remain available in the iCode project. If information is missing or you encounter another issue, contact NIH-OPA_Support@nih.gov or use the Feedback button in iCode.
For more information about using iCode, see the following resources:
You can also use the search function in the iCode User Guide to find additional help content.
Comments
0 comments
Article is closed for comments.