Currently we just say "use AQL", which will be unsatisfactory for less technical users. See comment for details.
(edited by @waxlamp to add): We should also consider whether redirecting the user to Multinet is the right thing to do. I think a better solution in general would be to allow the user to change some parameters in place: for a misspelled network name, we could just present a dropdown of existing networks. We could expand that to a general mechanism that allows for selecting both a workspace and a network. Then, the "sideloading" behavior would just be a special case of opening the app via query arguments. For "data too big" we could offer a ready made AQL query that samples the network down to the size limit by starting from a random or high-degree node. The associated error messages could then link to documentation for how to do this type of sampling, etc., yourself.
Currently we just say "use AQL", which will be unsatisfactory for less technical users. See comment for details.
(edited by @waxlamp to add): We should also consider whether redirecting the user to Multinet is the right thing to do. I think a better solution in general would be to allow the user to change some parameters in place: for a misspelled network name, we could just present a dropdown of existing networks. We could expand that to a general mechanism that allows for selecting both a workspace and a network. Then, the "sideloading" behavior would just be a special case of opening the app via query arguments. For "data too big" we could offer a ready made AQL query that samples the network down to the size limit by starting from a random or high-degree node. The associated error messages could then link to documentation for how to do this type of sampling, etc., yourself.