Is your feature request related to a problem? Please describe:

We would like to handle different cases in which users who are confident in a certain list of ML to AU match crosswalk can submit this as an argument input to a TADA function to prioritize this list, but still use other TADA Module 2 functions, such as TADA_GetATTAINS() to provide a match of other ML to AU that has not already been defined or as recommended matches.

Describe the solution you'd like:

1. We can have a flagging column to label a 'user supplied ML to AU' crosswalk to rank the priority. Perhaps label Rank 1 as a "High confidence in this ML to AU" crosswalk. Additional rankings can perhaps be determine with cases in which a ML site is assigned to multiple AU from TADA_GetATTAINS and ranked accordingly by distance?

2. If a user supplies their own crosswalk and TADA_GetATTAINS recommend a different ML to AU assignment, then these dup row matches can be flagged and labeled as "Matched From TADA Get_ATTAINS" or "matched from User Supplied crosswalk"

3. Handle cases of new AUs should be considered as well. Other labels can be merged, split. existing