Explore our programs — offering exceptional academic preparation, opportunities for growth, and the tools to make an impact.
Find everything you need to apply for and finance your graduate education.
Stories, strategies, and actionable knowledge — putting HGSE's powerful ideas into practice.
With deep expertise that connects research, practice, and policy, HGSE faculty are leaders in the field.
Get to know our community — and all the ways to learn, collaborate, connect, develop your career, and build your network.
Faculty-led programs to deepen your impact and build your effectiveness as an educator and leader.
Access the premiere education subject library for Harvard University.
Access the Office of Student Affairs, the Office of the Registrar, Career Services, and other key resources.
Explore opportunities to grow, build connections, and create change.
Migration was handled prior to launch and during support period most "migration" fields have been removed from the system. Currently there are a number of "Migration" related modules still enabled to handle some important linking functionality explained below. These modules include, but not limited to:
In order to handle some linking between content, some custom functionality was created for this migration. That was the creation of a "Migration Link". In short, a link was created with the OLD nids and on request, the link will redirect you to the new content, if available. If enough available data was present in the migration, the link could even "self-heal" itself. This functionality reduces the need for multiple passes in migrations and preserves functionality and reduces broken links. It is the intent that these links will and should be cleaned up.
In some link fields you may notice a link with this pattern, "/mig-link?orig=/node/40179". The origin url parameter will indicate the original link from the D7 site. The controller for this url will try to determine where this old node was migrated to.
If a link can be resolved, a notice will be logged so you can update the referring page.
If a link cannot be resolved, a notice will be logged.
You may notice some links with more url parameters. If those are present, the controller will try to "self heal" the link with the new link. Meaning, it will try to load the node, and update the link field with the new destination.
The custom code can be found in the hgse_utility module. And the main controller is Drupal\hgse_utility\Controller\MigrationLinkFixer
Drupal\hgse_utility\Controller\MigrationLinkFixer
The main fields this was used for, but not limited to were: