ETT-1484: remove alicorn from collection transfer - #247
Open
carylwyatt wants to merge 8 commits into
Open
Conversation
moseshll
approved these changes
Aug 14, 2026
moseshll
left a comment
Contributor
There was a problem hiding this comment.
Transfer on dev-3 succeeded with nary a hitch, JS console didn't even yell at me. APPROVE
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the second attempt at removing alicorn from the collection transfer process. The first version was much more complicated, although we didn't think it would be when we started. This is a simple, minimum-possible-changes version of removing alicorn from collection transfer. Even though this is simpler, I still added a lot of markup changes, most of which are utility classes sprinkled all over the XSLT.
I was very tempted to refactor this whole template, but in order to get this done quickly I did not do that. The template is scattered and confusing (to me), so I apologize in advance for the mess.
Ultimately, this is a stop gap measure and we should come back and fully redesign this process when there is capacity and/or a new version of collection builder.
changes
class="d-flex flex-column mb-0 gap-3"etc.)utils.jssince we don't need any of those click events anymore (no modal to close, different implementation of copy-to-clipboard)to test
Head over to dev-3, log in to HT, and go to your collections. If you don't have one, make one in order to test. It doesn't even have to have anything in it.
the end!