PRIORITY - ALWAYS Lowest level stuff first
=-=-=-=-

todo: change trial detection route that client first hits
	- make it a different controller and renamed to something like server ping or "hello" or something friendly and useful
	- maybe the route that gets Notifications
		- because there could be a notificatoin type that doesn't need logged in users for general server down announcements etc	
todo: Search get search result for workorder descendents doesn't fit into existing system due to it being a biz object wide feature but workorder having sub-get results
		- CHILD objects need to point to their parent and be readable in code for searching and for opening objects based on child object
		- so all child objects need a typeandid of the immediate parent
		- 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: add long polling notification route (CLIENT AND SERVER)
	https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3507
	- Need way to acknowledge receipt of long poll info from client to server so that it can be removed or something?
	- maybe successfull sending clears it regardless of client?
todo: ability to mass tag items from list (SERVER AND CLIENT)
	- also a good way to do an initial implementation of a mass ops UI code
todo: ability to mass rename a tag to something else in all objects (SERVER AND CLIENT)
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: 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:aycontext clean up old block of weird definitions
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: 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: OPS routes (SERVER AND CLIENT)
	- Backup, restore https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3369
	- These need to be done fairly early on in order to have shit to play with for testing etc
	BACKUP & related stuff that should be in v.initial release https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3369
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
	https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3367 <--time limited accounts for support or temporary access?
	https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/2059 <--- time restricted accounts so user can only login during business hours (still to be considered)
	2fa stuff, some logging and lockout stuff
	Go through the auth related cases and notes in client side and implement or close
	todo: 2fa? (if not in first release, is there something needed to support it in future dbwise?)
	todo: Auth Backdoor reset password feature
		how to code it here, pretty easy to do:
		https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3250
todo: Look into 2fa
	https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3395
todo: look into how to use an SSL certificate with the RAVEN server directly when not behind nginx
	- this should be supported by default out of the box working with Let's encrypt ideally
	- is it now considered ok to host .net core web api directly internet facing?
todo: onboarding and default manager account password
	- Need to come up with a safety plan for this so people don't leave it at default
	- Maybe the very first thing required of a user is to change the password before any tasks can be performed
	- Server stays in safety lock until they set a password?
	- Or maybe a random password is generated on seeding and somehow provided to user through console or something?
	- Maybe an empty db if no other users can be set password only so no one has made a hidden backdoor user account before ops changes it?
	- maybe tied to license if licensed so they bring some info they have from rockfish / their license purchase or something?
	- don't want it to be onerous too much and have some very inexperienced users so...
	- see what other programs do, like our forum software
todo: API docs, make separate page for datalists and remove from api-response-format.md doc but put a reference link to it there.

