Right now, if you link a character for logistics but they dont have the necessary corporate roles, you see a 403 page. This is undesirable. It should be possible to prove upfront that the character in question has the specific role (I think there is a TODO in the http/auth/eveapi.go about this).
Additionally, if a character does have high enough access, they should be able to establish a corporate level API account (probably going to need a legacy API key) that is continually used in background workers to keep corporate informations up to date.
If the data is already in the DB, even a char that doesnt have roles can see it. It's only once we hit up the API that we find out they dont have the role. No bueno.
Finally, I think that it should be possible for a user to link many different characters for each role. Each function of the site should allow the user to change which character they are currently using.
Right now, if you link a character for logistics but they dont have the necessary corporate roles, you see a 403 page. This is undesirable. It should be possible to prove upfront that the character in question has the specific role (I think there is a TODO in the http/auth/eveapi.go about this).
Additionally, if a character does have high enough access, they should be able to establish a corporate level API account (probably going to need a legacy API key) that is continually used in background workers to keep corporate informations up to date.
If the data is already in the DB, even a char that doesnt have roles can see it. It's only once we hit up the API that we find out they dont have the role. No bueno.
Finally, I think that it should be possible for a user to link many different characters for each role. Each function of the site should allow the user to change which character they are currently using.