in reply to design advice, please.
We are all gurus, some are just not as far along as others.
All the things you ask are easy if tackled one at a time, for example."location (from a merge with a qip subnet dump to a .csv spreadsheet)"
just slurp in the file, and check for it's host name.
# slurp will return every line from the file in list context sub slurp{ local *ARGV;@ARGV=@_; <> }; print grep m/$host/, slurp $csv_filename;
Randal gave me &slurp.
If you are going to perform the lookup more than once per run of the script, you will want to stash the lookup info in a hash or similar... But once you've read the file, you could insert the data into a database, and slowly phase out support for the csv in favour of some small CGI scripts or a maypole application to allow folk to keep the data up to data.
If you slowly port each data source (where you can) into a table in your database, and attach a simple frontend like maypole (which will nearly automatically do the whole Create/Review/Update/Delete thing for free), you will end up with a single point to go to when you want to find out about things.
You are asking for many small things, so you can just solve each of them, one at a time, it's just like Tetris, really
[] [][] []
|
|---|