CTDA System Migration

Project Update, April 17, 2923



THE NEW CTDA is almost here!


Project Update, March 20, 2023

Check out the new home page design at: https://ctda.i8.dgicloud.com

Also look at the new bottom menus being populated to make navigation and information finding more available across the site.

Throughout this week we are cleaning up the test site so we can migrate the new pages to the production servers at UConn. We will delete all content currently in the test repository. Next we will ask each institution to create and upload a logo for their organization, and to set up their organizational “theme” colors.

Instructions will be provided on the site’s “For Content Managers” help pages.


In more news, new training sessions have been added and include Complex Objects like Compound, Newspaper, and Publication Issue, as well as Spreadsheet Ingest. Basic system training will also be available. Check Slack to get sign-up details.

Project Update, February 23, 2023

One of our goals for the new CTDA is to make the management tools more robust and useful. As part of that process, we have been working on the tools available to you from the “Groups” area of the web site. The Groups pages essentially act like the “manage” server in the i7 system. It is the place where you can manage your content and get information about your collections.

The i7 system was very limited in what content managers could do beyond just enter and edit data. The new CTDA has many more ways to visualize and interact with your collections data.We have recently revamped the Groups menu pages and are looking for feedback on the functions available in those menu pages, and how they work.If you are interested in reviewing and commenting on the new Menu Pages.

Follow the link below to a document that explains the new pages. Please send your feedback to the #general channel If you do not have a New CTDA test site login, please let us know and we will make you one.https://docs.google.com/document/d/1JfSjVZ79dkOpAJJZKSCI3L-oS8UEQcnuga3zkwN8xQQ/edit?usp=sharing


We look forward to your feedback!

Project Update, February 2, 2023

We are putting finishing touches on the public access and management web pages and gearing up for the migration.

As we said in the beginning, our goal is to create “feature parity” or better with the new system in relation to the current CTDA. We believe that we have designed a system that is much easier and versatile for content managers. It gives them many more tools at their disposal for ingest, management, and statistics and reports than the old system. The new Mirador viewer will allow more interactive access to a broad variety of content for the user, and the search interface is more powerful and easier to use.

Preservation activities have been similarly upgraded with a more robust fixity checking system in place--with the ability for content managers to see when objects have been checked.

Still, not all desired features will be available when we go live. We are balancing the desire to have everything perfect with the need to get the migration finished and move to the new system. Managing and maintaining two systems is simply not sustainable for us.

When things start to happen they will happen quickly, we are in the calm before the storm. But we promise to give you all as much warning as possible before any big changes or ingest freezes occur. We expect that by early Spring we will be looking back on this with fond memories!

Project Update, January 12, 2023

The holidays are over and we are all back at work. Jan 12 is the 1 year anniversary of the beginning of the migration process. However, migration planning has been going on since Early 2021 with the needs assessment project that produced the Assessment report that has been the roadmap for the project.

Right now most major systems are designed and coded, except for the Mirador viewer, which is still being developed in conjunction with the larger Islandora and Mirador open source communities. Our patience will result in a much better product. However, it does slow down our timeline.

We continue to refine the UI for both the public display and the management display. We are learning how to use and create Drupal Views to improve user experiences and give content and group managers more tools to understand their collections. We implemented Google Analytics and will create an interactive site where content owners can create self-service reports on content use. This will be available for testing soon.

We look forward to migration testing and the migration process. Although our timeline has slipped a bit, we are optimistic that migration and the changeover to the new system will occur in the first quarter of the calendar year.

We thank you for the patience and your participation in this exciting and complex time.

Project Update, December 9, 2022

CTDA training was a great success! About 50 people attended at least one of the sessions and learned the basics of working in the new CTDA. Thank you all for your great feedback and good humor. We learned as much as you all did!

A video of the training presentation will be available shortly. Also, look for the next training topic: Complex Objects: Compound, Paged Content, and Newspapers coming in early January.

In other news, the server hardware is configured at UConn’s data center, and we are awaiting installation of the system on UConn servers. Final details for the migration are being checked and re-checked. Our timeline has slipped a bit, and we are expecting migration now in early February, 2023. There WILL be a period of ingest freeze that may last up to two weeks, but more details on that will be available after migration testing is complete.

A new validating spreadsheet ingest template will be available soon. This new spreadsheet makes the process less error prone, catching many potential errors before the ingest process.

Project Update, November 21, 2022

Sign up for CTDA Training on the new system. This training is for anyone who will use the new CTDA system. There are five dates currently available, and more to come.

See you there!

Project Update, November 15, 2022

My how time flies. Spreadsheet ingest is being tested by the testing group, and we are working out the kinks and bugs, as well as creating documentation for others to use.

General training webinars for using the new system will start next week. See the general Slack channel for details!

We are still awaiting implementation of the Mirador viewer. This will significantly change the user experience for the better.

Project Update, October 21, 2022

Two important developments occurred this week.

First, the first servers for the production system have been set up at the UConn computing center. These servers will ultimately host the pre-production development testing system. For now they will serve as the testing ground for production configurations.

Next spreadsheet ingest specifications are complete and spreadsheet ingest has been enabled in the sandbox system. We are writing documentation and instructions for spreadsheet ingest and will release this shortly for user testing.

All-in-all two big steps toward migration and production.

Project Update, October 14, 2022

Work has resumed on the migration as dgi folks have had power and internet restored. Spreadsheet ingest is getting its final reviews, and we will be able to test this process soon. CTDA staff is working on developing training documents for training sessions to start soon.

We are working with UConn ITS to begin building the production hardware infrastructure. This is the last step before we can start testing the migration process and begin actual content migration.

Project Update, October 3, 2022

Power and Internet were out for most of the PEI area over the past week. We expect that they will return to work sometime this week. While this pushes our timelines back somewhat, the delay should not be significant. However, we will push i2 training sessions to late October, to give us time to get the management screens configured.

Stay tuned for more information as we have it!

Project Update, September 26, 2022

We don’t yet know the impact on the project of Hurricane Fiona, which hit Prince Edward Island over the weekend. PEI is the headquarters of discovery garden, our software support vendors. We expect it will be at least a week before they are back on line.

Meanwhile, over the past two weeks a lot has been happening. We are working on i2 training and expect to release the training schedule in early October for training sessions to begin shortly after.

We met with UConn ITS and mapped out the system specifications and timelines for hardware and storage arrays.

We are now working on building out a more useful and efficient set of management tools that will give our content managers more information about their collections, and greater ability to make bulk updates and do other maintenance tasks.

Project Update, September 9, 2022

Are you ready for i2 training!? The CTDA will begin offering i2 training webinars in late September. These 45 minute introductions to the new CTDA will teach you the basics of working with the Islandora 2 system that forms the basis for the CTDA’s software infrastructure. We will start with an introduction to new vocabulary, comparing the words we used in Islandora 7 (the current system) with new words in the i2 system. Then we will move on to understanding Groups--a new i2 concept, working with metadata, working with media, and how to understand the new content models. Check the #general Slack channel for dates and details coming soon!

In other news. The metadata profile is complete and mapping between the i7 and the i2 system is also complete. This combined with the final touches to the migration process means that migration testing can begin in the near future. Migration testing with test data will give us benchmarks for how long the migration process will take.

We meet with UConn ITS next week to go over hardware specifications for the production servers, and discussions relating to provisioning storage for the growing CTDA. (Did you know that the CTDA recently hit 100TB and is growing at a rate of 30-35TB per year? That’s a LOT of content!)

The current sandbox iteration of the i2 system uses the Open Seadragon viewer for text, audio, video, pdf, etc. This will soon be replaced by the open source Mirador viewer which has been waiting for completion of the Metadata and data modeling to be finished.

Final polishing of the public and management screens is in process. We hope to have that completed soon. As we bring up new documentation we will put it into the new Resource Center which will run within the CTDA i2 system and not on the external Confluence server. You will see a more unified and consistent navigation in this new set up.

As always, stay tuned for more information right here!

Project Update, September 1, 2022

Welcome to September! The long awaited specifications for spreadsheet ingest have just been shared from dgi. While not fully complete, the specification has a number features that will make spreadsheet ingest more efficient and less reliant on arcane knowledge of Islandora terminology.

Some highlights:

  • No need to remember complex content model strings, the new system uses plain language: Audio, video, image, etc. just like the metadata forms

  • Create compound, book, and other complex objects and their components in one sheet without having to assign unique IDs in advance. Details on how to do that will be shared soon.

  • Only ONE template for all types of content--images, newspapers, books, pages, etc.

  • Basic Template may be used as is or augmented with added fields that you can add yourself from the list of all field indicators. No need for massive numbers of field columns, have and use only the ones you want.

  • Streamlined attribute and content matching. Instead of keeping track of what position an attribute term is in you will now use syntax to add them in order, for example: Person 1|authority:lcnaf; Person 2|;…

Full specifications and examples coming soon. As soon as the specifications are implemented, we will be looking for volunteers to test the process. And remember it was your use, feedback, and patience that has resulted in the improvements to the system!

The presentation layer design is entering its last stages with final adjustments to themes, displays, and Group features being implemented. The Groups feature allows for a lot more individuality in presentation while preserving many standard elements for continuity. Check out the current look at: https://ctda.i8.dgicloud.com.

Project Update August 19, 2022

Namespaces and PIDS

Namespaces and PIDS have been an integral part of the CTDA from the beginning. As you know, Namespaces are the numerical designation for your organization that combined with a PID creates a unique identifier within the Islandora/Fedora system.

The new system architecture does not use the Fedora infrastructure to manage preservation/audit/and fixity activities. These are taken care of by native Drupal and Islandora modules. This means that Namespaces and PIDS will not be a part of the new system.

Groups replace Namespaces as the organizing structure in the new system. Node identifiers become the new PIDs and relationship mapping connects a Repository Item to its Group. Nodes are assigned as a numeric string in consecutive order, regardless of ownership or object relationship. Content managers will NOT be able to assign their own PIDS as they do now.

During the migration, ALL repository objects will receive node identifiers. Namespaces and PIDS will be retained (but not viewable) for the purpose of Handle mapping and other system processes.

This change has a number of effects. First, Repository Item ownership may now be transferred from one Group to another. This was impossible previously using the namespace system.

Next, spreadsheet ingest becomes much easier because you will not have to create a PID for a parent object (Book, Compound, Newspaper Issue, etc.), or ingest your parent objects before the child objects. New spreadsheet ingest process will do that automatically (Exactly how to do this will be published soon)

Third, it will be easier to create shared and topically based collections using Groups and will allow us to more granularly assign management permissions to Repository Items and Collections, collaborative work easier.

From a public user point of view, nothing will change, from a management perspective we will have a much more streamlined system, but it will NOT be possible to look at a URL and know who owns an object as you can now. Updated August 24: URLs for repository items will be automatically assigned a “URL alias” which is a human understandable--more or less--text string. For example: https://ctda.i8.dgicloud.com/stone-duck. The URL will not contain breadcrumbs leading back to the sub collection, collection, group and such in the URL. The NODE ID is available on the management screen for content managers who need it. For example: https://ctda.i8.dgicloud.com/node/158 but only the URL alias will be displayed to the public.

We think these changes will make managing and organizing CTDA content easier and more efficient for everyone.

Project Update August 18, 2022

Spreadsheet ingest is in final stages of development and QA testing. We should have a process ready in a week or so. Like so many things spreadsheet ingest will be far more flexible than the current version. The templates will be user editable and we will offer templates for different levels of metadata, from minimal metadata to “extreme” metadata and everything in between.

Project Update August 8, 2022

Taxonomy configuration and bulk loading to taxonomy lists capability is complete. This allows us to move to spreadsheet ingest configuration in the next couple of weeks, this needs to be complete before migration begins.

Refinements to the presentation layer continue. Join the coda-web-design-testing channel to keep up with the latest news and updates. https://ctdigitalarchive.slack.com/archives/C03GD5T2TL2 We really want your feedback!

Project Update July 27, 2022

Two interesting updates:

  1. The project timeline remains on schedule for migration to begin in Late August or Early September. The exact shape of that migration is still being determined. Right now, there may not be an ingest freeze at all, but that is still to be determined. The GOOD news is that new workflows are much more streamlined and most ingest, collection creation and editing tasks have far fewer steps than in the current system.

  2. The new system will not have a “public” and a “management” website. All management activities will take place by logging into the “public” site. This will alleviate some of the issues of synchronization we see between the public and management sites (like thumbnails not displaying correctly). Updates and changes will be immediately reflected in the system.

Project Update July 25, 2022

Well, it has been a while since our last update. Lots has been going on, most of it behind the scenes. The CTDA metadata profile is complete and has been integrated into the test system. This means that all the metadata fields from multiple schemas have been mapped and crosswalked to each other, to the MODS schema, and to the metadata display configurations. We are happy to report that the CTDA will now be able to display Darwin Core metadata and labels on public pages.

Metadata normalization in preparation for migration continues as well. We are going though hundreds of thousands of metadata records fixing technical issues such as records without required fields, or records with content in the wrong field. Many of the inconsistencies come from older records or from spreadsheet ingests that had content in the incorrect column. In the future we are going to have “metadata management parties” on a regular basis, to keep the database consistent in structure.

Third party ingest workflows are proceeding as well. The new workflow will combine three current processes into a single workflow for ease and convenience.

The Feature Testing Group (Slack channel #feature-testing if you are interested in participating or following along) is testing bulk addition of taxonomy terms, so that our choices in descriptive metadata can be more diverse.

More development on the display design has also been deployed. The “system level” header is now part of the display. This separates the system menus from the collection specific menus and navigation.

Other upgrades to the landing page include behind the scenes updates to the gallery, the featured objects, and the “brought to you by” section. Check out the updated, but still not finished look: http://ctda.i8.dgicloud.com



Project Update, June 14, 2022

Latest iterative design for collection and object pages are available here: https://xd.adobe.com/view/21823df5-0689-473e-ad83-1b5d076ad532-74d1/ . Click on the comments for an explanation of the changes.

Checksum and Fixity checking are in final stages of review.

Taxonomy mapping is the next feature that will be tested. We are examining the ability to bulk load terms from external vocabularies, including vocabularies from non-customary domains. This is supported by research being done by Rachael Nutt for the CTDA in Context project. Our current list of potential vocabularies is available: https://docs.google.com/document/d/1CPelIcZvit4ghR4D5Zms_tTnk6PTUlYieUl34ZwxYxY/edit#

Project Update, June 8, 2022

I can’t believe that it has been almost a month since the last project update! Lots to report. The metadata profile is finished, thanks to all on the metadata review group for all their help.

Presentation layer designs are progressing. The most current iteration is here: https://xd.adobe.com/view/bd1b11d7-e85d-40e6-95b1-d261575227de-e848/ although that could change quickly

The Mirador viewer implementation is waiting for development work on search term highlighting in full text to be completed. This is a NEW function for the open source Mirador viewer and the code we develop will be contributed to both the Mirador and Islandora open source communities.

New features being implemented include the new “Groups” feature which allows top level collection owners the ability to manage the logo color scheme of their collections, as well as manage their own user accounts. And even more exciting, Group managers will be able to configure the layout of their item level pages themselves. (So if you want the metadata to display first, second, on the left, on the right, etc. it is your decision!)

Other backend developments include implementation of checksum checking and fixity checking that ensures the authenticity of your content.

Coming soon will be implementation of presentation designs in the CTDA Sandbox.

Project Update, May 11, 2022

Not much news to report, the metadata profile is nearing completion, just a few details left. This includes decisions about taxonomies and how they will work in both management and facet displays on search results.

Preliminary work has begun on the Presentation Layer, beginning with a redesign of the “Front” page, or the landing page of the entire site. We will be putting out a call for volunteers to review our design and information architecture ideas shortly. Stay tuned!

Project Update addendum, April 22, 2022

I forgot to mention that the new system will be implementing the Mirador viewer for all supported object types. Mirador is a community developed, open source viewer that allows for highly customizable presentations of content that are user configurable. A good example of how Mirador handles text navigation and highlighting is here: https://mirador-textoverlay.netlify.app Note that clicking on the "Hamburger" icon on the top left will toggle the metadata, and you will be able to click around on other icons to change the display interface. The specific features available on our implementation are yet to be determined.

Project Update, April 22, 2022

The Metadata Review group has finished its analysis of the metadata crosswalk between the current system and Islandora 2. A document will be available soon. The new system allows us to customize metadata management to our local needs while still remaining consistent with national standards based on MODS. Not surprisingly, the review turned up a lot of “non-standard” metadata, mostly in the form of typographical errors and adding good terms into the incorrect fields. Mike and Heather are working on metadata normalization.

Feature testing continues as. new updates come available. Most work is being done on backend systems. Feature testing has been completed on Collection search configuration, and versioning, as well as fixity checking, and checksum generation.

Feature testing will ramp up as metadata standards are implemented in the system and we begin to work on presentation information architecture and theme development.

The new Groups feature being developed will allow members to manage not only their user accounts and individual permissions, but also provide a browser-based way to manage your collection’s color scheme, logos, and other aspects of your organization’s look and feel to the public if you so choose, giving every member many of the features of an independent site while remaining within the CTDA system.

Project Update, March 21, 2022

Both the Metadata review and the Feature testing groups have been formed and have had at least initial meetings. Both groups have open channels in CTDA Slack (#feature-testing, #metadata_review) if you are interested in following along, and if you want access to the documentation from dgi about testing or metadata please ask us at the CTDA for read access to the Google drive.

Project Update, March 4, 2022

Most questions relating to storage, checksum checking, and meeting preservation standards have been ironed out. Next up on the agenda are two areas that begin to touch content managers and end users: Metadata profile and functionality.

We will put out a call next week for metadata experts to review the proposed i2 metadata profile. The new CTDA will not store MODS records as xml data streams but in database tables and nodes in the Drupal system. Content managers will still work in the MODS schema on the front end and in spreadsheet ingest, but how the data is managed will change. the MODS profile will translate our MODS language into database language. We will be looking to our metadata experts to review these mappings.

Second, we have created a small group to test system functionality. Led by Anna Newman (CSL) and including, Molly Woods (CHS), Sean Parke UofH, Betsy Pittman (UConn), and Tina Panik (Avon PL), this group will begin testing core functional elements of the i2 system as they are released to the test server. These will begin with fairly mundane activities like logging in, adding a user, creating permissions, creating objects, using metadata forms, and such. After preliminary testing of the system is complete, we will open the site to read-only access to all members. Once the system is stable, probably this summer, we will begin training on using the i2 system.

The testing group will be very interested in your feedback and will be communicating with the membership as they go along.


Project Update, February 21, 2022

The last couple of weeks have been spent looking at questions relating to preservation, storage, checksum, and other deeply buried foundational frameworks that most users will never see or need, but must exist to guarantee authenticity and reliability over time. These “not shiny” parts are the heart of the preservation system.

Additionally we are also implementing a “sandbox/development” site that will begin with an out-of-the-box implementation of the Islandora 2 system. This system will be enhanced with features specific to the CTDA as illustrated in the feature list at right and in the spreadsheet. As soon as the sandbox is ready, we will open for read only access, so members can get a look at the beginnings of the new system. NOTE: The sandbox will NOT have the CTDA theme implemented at the beginning. That will come later.

Project Update, February 4, 2022

Next week we will start working on presentation layer theming in the test environment and metadata mapping.

A Note on Metadata

Although we will still do our work within the MODS metadata schema, the data will no longer be stored in mods-based xml files, but in data tables in the Islandora system. This is more efficient for the system and will result in enhanced performance. This change will not affect our day-to-day work in the system as MODS elements will continue to be the basis for our metadata forms and spreadsheet ingest metadata. When MODS records are required, such as for DPLA uploads, those MODS files will be generated by the system.

Project Update January 14, 2022

The project officially began with a kickoff meeting between the discovery garden team and the UConn project team on January 12, 2022.

Project Update, December 1, 2021

We continue to wait for UConn’s purchasing and contracts unit to give final approval to begin work. 

Project Update, November 1, 2021

Our project timeline is on hold while we wait for UConn's purchasing and contracts department to give the final OK to the contract with discoverygarden to implement the system migration.

Project Update, October 1, 2021

We have created a spreadsheet to connect items mentioned in the Final System Analysis Report from dgi to features and activities we are all used to doing in the current CTDA system. Like many spreadsheets it can be hard to read in its current PDF form. But we wanted to get something out there in case people had questions. 

The spreadsheet has a column called "WBS Item" which links the feature on the left with the Item in the Work Breakdown Structure of the Final System Analysis report received from dgi.   If the WBS column says "Core" that means there is no specific WBS activity for this feature, it is part of the standard installation. Another column labeled "Parity or New Feature" explains the nature of the feature and if it is enhancing old i7 feature, or is new to the system altogether. 

Project Update, September 10, 2021

The final analysis report from discoverygarden was approved by the CTDA in the first week of September. This report is now available.  The report is filled with technical language and jargon. We will produce an executive summary of the report written in non technical language in the coming days. 

The Ultra-condensed version is that we are focusing on "feature parity" as a first step for the new system. That means that we are going to ensure that everything you can do now in the CTDA you will be able to do in the new system. This is more difficult than it may seem since the underlying method of data management is much different from how the system currently manages data internally. 

Because of the amount of work we did developing the assessment report and roadmap. We can move directly to implementation, saving months of analysis and planning time. 

The Project

The CTDA is embarking on a major upgrade to its infrastructure to bring you better service and more features. Our current Islandora 7 system was originally installed in 2011 and runs on three core open-source tools: Islandora version 7, Drupal version 7, and FedoraCommons version 3.6. All three of these systems will be discontinued in 2022. We started planning last Summer to migrate to more up-to-date versions of these software applications and wanted to report our progress to date and solicit feedback in some areas.

Current Technology

First, we will be expanding the technology architecture of the CTDA system. The current system, implemented in 2018, was scaled for approximately 50TB and 1.5 million objects. The current CTDA has over two million objects, and we have all been aware of slowdowns in the system, especially in derivative generation on the back end. The new infrastructure will be scaled for a Petabyte-sized system with millions of objects and will have the ability to automatically balance the load of system resources based on demand. We should see significant improvements in system performance and continued good performance as the system grows. We will be working with UConn ITS to implement the new technology infrastructure.

Migration Roadmap

Next, we worked with our software support vendor discoverygarden (dgi) to analyze the current system and create roadmap for migration to the new system that preserves a “one to one” feature set between the two. That is, all current features available in the CTDA will be available in the new system. Some of these features may work a bit differently behind the scenes, and there will be some changes in how certain things are done in the new system. We will develop training programs and documentation in the Resource Center to smooth the transition. Islandora 8 (as it is called) also comes with a host of new features already built-in. 

A few of the new features that are standard in Islandora 8 include:

  • A Taxonomy feature that will make metadata management easier, faster, and more responsive.

  • A redesigned management interface which will make content management easier to understand. This new interface uses a “common sense” approach to content management without the need to understand obscure things like “RelsExt” datastream terminology and syntax.

  • A new “universal media viewer” that supports all types of multi-object content, including books, newspapers, and compound objects in a streamlined interface

  • A browser-based, user friendly “batch update” tool, that will allow you to make metadata updates to multiple files at once.

New CTDA Features

Finally, we want to take this opportunity to implement new features in the system to enhance the user and content manager experience. While we have many ideas of our own, we want to hear from you. We’ve created a Islandora 8 wishlist channel in CTDA Slack for you to contribute your wishes. And since this is a “wish” list, don’t worry about how we might do what you are asking, or what it would cost. We just want to hear about it. We hope that this wish list will spark conversation among the membership about what you want to CTDA to become.

Project Timeline Overview
(July 2022)

The project officially began on January 12, 2022 with a kickoff meeting between representatives from discovery garden and the UConn project team. The following list is an high-level overview of the activities in each phase with the approximate date of completion for each phase. Items with strikethrough text have been completed, tested, and implemented.

The project will proceed through five phases:

  • Implementation Planning (February 1)

    • Finalize the activities of the other planning phases

  • Infrastructure and Installation (March 15)

    • Deploy a “sandbox” environment on UConn servers

    • Configure hardware infrastructure with UITS (moved to later in the process)

    • Install Islandora framework and stack components (moved to later in the process)

    • Meet Core Trust Seal requirements

  • Presentation Layer Configuration (March 15)

    • Member collection branding

    • Collection limited search

    • Collection search in page header

    • Representative object view configuration

    • Member item branding

    • Paginated item display with interaction (waiting for development)

    • Newspaper display and interaction (waiting for development)

    • Iterative refinement and theme completion (in process)

  • Functional management Configuration (July 15)

    • Permissions and access: Groups (in process)

    • Media versioning

    • Checksum features

    • Taxonomy updates

    • Content type updates (in process)

    • Third party ingest process (combined a number of other processes into one 6/2022)

    • Handle service

    • Multipage CVS ingest rows

    • Manuscript content support

    • Bulk application of embargoes

    • Extracted text hit highlighting for paged content

    • IIIF/embedded frames in external web sites (added 1/2022)

  • Migration (August 23) (Late September)

    • Migrate I7 repository object metadata and files to new system (not necessary)

    • Maintain fidelity of metadata, digital files, and object relationships (in process)

    • Create taxonomies

    • Migrate current taxonomies (added 7/2022)

    • Remap Handles for all repository items

    • Retire outdated domain names

System tuning and testing will begin in late August. Organizations will be migrated individually beginning in August, so there will be a time when some groups are “live” in the new system and others are still “live” in the old system.

We are expecting to build the production system in Late September and begin the migration process shortly after that.

Following the last organizational transfer, the new system and the old system (with no updates) will run in parallel for a time to be determined. Final retirement of the I7 system is expected no later than December 31, 2022.