BoldMinded acquires Ansel, support ending for all add-ons. BoldMinded acquires Ansel, support ending for all add-ons. Read More →
Support has been discontinued. Issues remain available as an archive. Support has been discontinued. Issues remain available as an archive.
Ansel/Treasury Data Migration Method?
#101 opened by Digital Designs
Description
We are migrating an older client site (currently EE4 using Ansel/Treasury) from a multi-channel site with hundreds of content creators, to a new EE4 site with a single channel ("Combined" site) in an effort to streamline content entry for clients.
The Ansel field uses Treasury locations (AWS backed) and contain a significant amount of images using 2 buckets - "Originals" and "Edited" (for the cropped versions). These same locations will be used in the exact configuration for the "Combined" site.
Both sites utilize the Ansel field for this gallery function.
We are using Datagrab to migrate the entries, however need to identify the best way for the new entries on the "Combined" site to have Ansel/Treasury awareness of the existing content and correlated correctly with original article.
Is this possible, and what might be the best way to go about this?
Replies
- TJ Draper
Replied 4/16/2018 10:50 AM, Edited 11/10/2018 9:53 AM
Alright, so here's the high overview of the data structure:
- Ansel has one row for each image in a field
- That row contains the entry ID, field ID (and possibly row ID and column ID for Grid/Bloqs)
- The row also contains the file IDs of the images needed for that row. This includes the original (source) file ID, the generated file ID, and the thumbnail file ID.
- For its part, Treasury has a row for each image. Since you're images are all on AWS all you need is for the locations on your new combined site to be set up correctly, and bring the rows for those images over and associate them with the correct location(s) you set up in Treasury.
- Then you should be able to insert Ansel's rows and associate them with the correct entry IDs and field IDs.
The tricky part is all associations are based on primary key, which may be different depending on how you get that data into your new site's database. But there should be ways of importing those rows that retain the previous primary key.
Does any of that make sense? :)
- Ansel has one row for each image in a field
- Digital Designs
Replied 4/16/2018 11:33 AM, Edited 11/10/2018 9:53 AM
It sure does, and clarifies that we will either need Datagrab to be aware of this architecture (not just see it as a single field), or utilize another migration method. Thanks!