re-org todo
This commit is contained in:
@@ -1,12 +1,21 @@
|
||||
|
||||
TODO: PRIORITIZE ALL THE FOLLOWING INTO TWO CLASSES - "NOW" or "LATER"
|
||||
then do the "now" ones
|
||||
=-=-=-
|
||||
|
||||
### NOW
|
||||
|
||||
todo: add query fail logging to datalist just like done with picklist so in production can catch mysterious problems more easily
|
||||
|
||||
TODO: BizRoles.cs seems to get hammered on every single request, is it efficient?
|
||||
- Why is it not cached in some way?
|
||||
- Look into Lazy initialization (i.e. private static readonly Lazy<IDictionary<string, string>> mappings ....etc)
|
||||
|
||||
todo: CHANGE TO A DEDICATED SPOT IN GLOBAL RATHER THAN INFERRING AS IT IS NOT RIGHT PRACTICALLY for reasons
|
||||
todo: AUTO ID GENERATOR
|
||||
change to a dedicated spot in global rather than inferring as it is not right practically for reasons
|
||||
Get the auto-id most recent values at boot time
|
||||
internal static void SetMostRecentAutoIdValuesFromDatabase(AyaNova.Models.AyContext ct)
|
||||
todo: search tables in schema, I think there is a missing index here, need to look at the search query section again as it was changed several times from the original schema creation
|
||||
|
||||
TODO: API REFACTORING (note: workordercontroller / biz should be following all these rules so it's the template if need reference)
|
||||
todo: consider and then get rid of PATCH in all routes
|
||||
unless compelling reason to keep
|
||||
@@ -34,19 +43,15 @@ todo: Search get search result for workorder descendents doesn't fit into existi
|
||||
- Not sure where to document this so putting it here for reference
|
||||
- Required for opening a search result of a descendent that is not directly openable an
|
||||
- Need parent AyaType as an ENUM ATTRIBUTE in the AyaType table for easy traversal
|
||||
todo: search tables in schema, I think there is a missing index here, need to look at the search query section again as it was changed several times from the original schema creation
|
||||
|
||||
|
||||
todo: some kind of ops specific event log or system that triggers alerts to ops people, I guess notifications would be the word I'm looking for...
|
||||
- Once that exists a lot of backfilling needs to be done for example attachment files missing notification etc etc etc
|
||||
todo: api / server landing page is shitty on a mobile
|
||||
and really just shitty, add a logo or some shit
|
||||
todo: Should server show uptime somewhere?
|
||||
todo: VET translations
|
||||
- There are still a large number of non translated items in the non english stock languages
|
||||
- Make it easy to dump the local storage translation text for vetting the translations (at the client did I mean?)
|
||||
- Login as each language, exercise the entire UI and then dump all the translation text that was fetched from the server and look for non english words
|
||||
|
||||
todo: BACKUP & related stuff that should be in v.initial release https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3369
|
||||
todo: there are several outstanding AUTHENTICATION related cases in rockfish for RAVEN
|
||||
|
||||
todo: (BREAK THIS OUT INTO LATER/NOW/CASES) there are several outstanding AUTHENTICATION related cases in rockfish for RAVEN
|
||||
e.g. https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1924
|
||||
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1835
|
||||
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1998 <---this is an important case for consideration
|
||||
@@ -59,33 +64,37 @@ todo: there are several outstanding AUTHENTICATION related cases in rockfish for
|
||||
how to code it here, pretty easy to do:
|
||||
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3250
|
||||
|
||||
TODO: HOw is it that I'm able to login and view widgets while the server is seeding?
|
||||
- is it because I'm logging in with full ops rights?
|
||||
- shouldn't it be locked out for any non-ops actions?
|
||||
- maybe if get server closed return value from any operation then
|
||||
check if user has ops rights, if so go to ops server status page directly
|
||||
if not then go to ops server status page...?
|
||||
need an ops server status page!
|
||||
- There should be some kind of client UI that handles this like an overlay on screens where there is no access or a redirect to an no-access page or something
|
||||
|
||||
todo: Server ops EMAIL address for server to send health messages to!!!!
|
||||
- also maybe whatever other methods people use these days (text?)
|
||||
- Boot config setting
|
||||
- maybe this should be mirrored as a setting in global biz admin as well because the biz admin needs to know about critical server issues or impending doom of the server (disk space etc) just as much as OPS
|
||||
- also OPS people are not always trustworthy
|
||||
|
||||
TODO: check non-ops user can login during seeding operation
|
||||
todo: Log configuration into server log at startup? https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3523
|
||||
log all config settings into server log on boot
|
||||
|
||||
|
||||
todo: Event log pruning
|
||||
- at least make a case for it, it's going to be needed if not in the first release
|
||||
todo: add a post backup maintenance job (or very long periodic built in job that rarely runs) which does the following:
|
||||
Search dictionary: Auto remove orphaned words https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1878
|
||||
TODO: Is there a log that records past jobs, how long can they be viewed?
|
||||
TODO: Rename the link to AyaNova App on the server page to just "AyaNova"
|
||||
TODO: translation cjkindex, no way to set this value currently
|
||||
TODO: translation cjkindex, no way to set this value currently
|
||||
TODO: Licensing - make sure tech type use license works properly: a tech license is consumed if a user has **any one** of the four roles of TechFull, TechLimited, SubcontractorFull, SubcontractorLimited
|
||||
TODO: JobsBiz::Create -> should log an event in order to be able to see who created a job, but maybe not for automatic internal jobs
|
||||
|
||||
TODO: API docs, make separate page for datalists and remove from api-response-format.md doc but put a reference link to it there.
|
||||
|
||||
-------------------------------
|
||||
### LATER (TURN INTO CASES IN ROCKFISH WHERE POSSIBLE AND REMOVE FROM HERE)
|
||||
|
||||
todo: noticed Scott@4alarm has a daily job that just generates a dummy workorder so he can see that generator is working
|
||||
formalize that into a feature
|
||||
TODO: JobsBiz::Create -> should log an event in order to be able to see who created a job, but maybe not for automatic internal jobs
|
||||
high cycle recurring jobs should not log
|
||||
todo: add a post backup maintenance job (or very long periodic built in job that rarely runs) which does the following:
|
||||
Search dictionary: Auto remove orphaned words https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1878
|
||||
todo: Event log pruning
|
||||
- EVENT LOG **MUST** LOG the event of the user clearing out the event log!!!!!@
|
||||
- I see maybe deleting non-essential info first but keeping old CREATE event even if ditch a lot of fetched / modified events
|
||||
- Needs to be selective maybe?
|
||||
- at least make a case for it, it's going to be needed if not in the first release
|
||||
todo: VET translations
|
||||
- There are still a large number of non translated items in the non english stock languages
|
||||
- Make it easy to dump the local storage translation text for vetting the translations (at the client did I mean?)
|
||||
- Login as each language, exercise the entire UI and then dump all the translation text that was fetched from the server and look for non english words
|
||||
??: Built in automatic job available that will regenerate sample data on a timer for display purposes. Maybe need a board with a variety of built in automatic jobs to choose from to enable or not since there will likely be others.
|
||||
TODO: UNLOCALIZED TEXT
|
||||
- Look for old translation text keys that were not translated, there are more than a few keys that were added later to v7 and never translated out of english.
|
||||
- Some may never be used so be careful about this.
|
||||
@@ -93,15 +102,13 @@ TODO: UNLOCALIZED TEXT
|
||||
|
||||
todo: hang trial off of App.ayanova.com or make that domain and put a landing page there because it's going to be needed for self host eventually and trials now
|
||||
|
||||
-------------------------------
|
||||
MAYBE??????????
|
||||
|
||||
??: Built in automatic job available that will regenerate sample data on a timer for display purposes. Maybe need a board with a variety of built in automatic jobs to choose from to enable or not since there will likely be others.
|
||||
|
||||
|
||||
-----------------
|
||||
FUTURE
|
||||
|
||||
todo: some kind of ops specific event log or system that triggers alerts to ops people, I guess notifications would be the word I'm looking for...
|
||||
- Once that exists a lot of backfilling needs to be done for example attachment files missing notification etc etc etc
|
||||
todo: Server ops EMAIL address for server to send health messages to!!!!
|
||||
- also maybe whatever other methods people use these days (text?)
|
||||
- Boot config setting
|
||||
- maybe this should be mirrored as a setting in global biz admin as well because the biz admin needs to know about critical server issues or impending doom of the server (disk space etc) just as much as OPS
|
||||
- also OPS people are not always trustworthy
|
||||
TODO: API RATE LIMITING / THROTTLING (NOTE: THIS IS MOST IMPORTANT WHEN GET INTO SELF SERVE / HOSTING)
|
||||
- Return code 429
|
||||
- Going to need rate limiting to save people from themselves
|
||||
|
||||
Reference in New Issue
Block a user