Various Feature Suggestions

[rvtis]

I preface this with an apology that I am not a PHP programmer and could not get one, perhaps some thing could be edited in the raw database (char limits maybe?), but ultimately I nor anyone I know could implement any of these suggestions except maybe the char limits.

I have several suggestions that I have heard numerous times from non-admins relying on openDCIM a lot.

1. Separate field for rack number, perhaps even with toggleable visibility (like how rack labels can be hidden)
2. Stop the Enter button from selecting and going to the first result, it is REALLY, IMMENSELY ANNOYING that I or anyone has to click the magnifier icon to search a phrase because the Enter button LOVES to just push the first result in our eyes like some kinda desperate door-to-door salesman. Make Enter Enter Again (MEEA)
   
3. Re-assignable rack coloring - there are 3 rack colors and they're only for rack metric status (OK, high, critical), my colleagues agree that this coloring should be re-assignable to different functions: importance, availability (is it owned?), such and such. Or any similar solution of visual textless labeling that lets you at a glance see what's available.
4. Label length constraints: Why 20 characters? It's not enough! Not all customers have 4 letter names, and God forbid you got a DC number AND 4 digit rack number (see point nr.1) AND a long name. Example: "DC3-204-Data Logistics Communications" (imaginary company name that is about as long as one of our REAL customers, who I obviously not gonna name). That will NEVER fit the label field! Ever! Not until size constraints and rack.nr. separation is implemented.
5. Most reports are only in PDF, there should be at least Excel and perhaps even XML available. A selector of which format to use. Would be a blessing for anyone analyzing the data across many DCs with hundreds of racks!
6. Idk if this is a bug or a feature but reports don't support special characters, even though the host server does, this should be fixed. Not sure if it's on me or on you.
   6.5. Looking at point nr.2, I see that symbols aren't supported either: "thing" becomes &#32thing&#thirtytwo (github is adamant about turning every #number into a ticket link)