Latest revision as of 23:04, 25 March 2010

Some General Questions

Doing some preliminary research for the upcoming seating chart app. Just looking for feedback, comments. Sorry if many/all of this has been covered prior to my arrival. Just trying to get up to speed on this one before I start work on it.

Goal is to evolve this page into a sort of requirements doc for this.

Proposal

Component I : Floorplan editor

Display an image of the floor plan in a Web interface.
User can assign landmarks (seats/desks) on the image by simply clicking on a point

Questions?

do we even need to define 'seats' Is it okay to just have emp icons on the image of a floor plan
where do we persist this info

Component II : Assign Emp to Seat (landmark)

In wed interface display the image with 'landmarks' layer
user can click a seat and 'assign' an emp to the seat
- could also remove an emp (and place them elsewhere)

Questions?

where do we persist this info

Component III : Confluence of The above with the Moz phonebook

Seating chart location becomes an ldap field displayed on a phonebook record
clicking the link takes you to the floorplan image with emp's seat in focus
in on the "view the seating chart, we enable URI like this

.../seating/skeen@mozilla.com
we would not need to add any fields to Ldap

@@ Line 1: / Line 1: @@
-''Doing some preliminary research for the upcoming seating chart app.'' Just looking for feedback, comments Sorry if many/all of this has been covered prior to my arrival. Just trying to get up to speed on this one before I start work on it.
+= Some General Questions  =
+''Doing some preliminary research for the upcoming seating chart app. Just looking for feedback, comments.'' ''Sorry if many/all of this has been covered prior to my arrival. Just trying to get up to speed on this one before I start work on it.''
 Goal is to evolve this page into a sort of requirements doc for this.
-= Some General Questions  =
+=== Proposal  ===
+==== Component I&nbsp;: Floorplan editor  ====
+*Display an image of the floor plan in a Web interface.
+*User can assign landmarks (seats/desks) on the image by simply clicking on a point
+Questions?
-=== Phases ===
+*do we even need to define 'seats'&nbsp; Is it okay to just have emp icons on the image of a floor plan
-Are we interested in Phase One (Google like map) Precision: Click Location in phone book and get a Map with pin at their location Phase Two Precision: If a facility map is available, Click Location in phone book and get the image of that facility with pin at emp's seat. With option to scale out to Map with pin at address.
+*where do we persist this info
-<br>
+==== Component II&nbsp;: Assign Emp to Seat (landmark)  ====
-=== How do we populate the data ===
+*In wed interface display the image with 'landmarks' layer
+*user can click a seat and 'assign' an emp to the seat
+**could also remove an emp (and place them elsewhere)
-''From the files that Ryan sent, it looks to be a Viso dump of the Image meta data that gives the positions of the network drops. Then there is a csv file that links emp to network drop. Was this a decided solution of how to get emps placed on the facility image or just proof of concept , trial and error? It certainly works, I was just curious if we were looking for a more real-time solution or we're good with this batch like solution.''
+Questions?
-*Is the manager expected to enter the data manually Are we interested in obtain the position of the seat from other data (at least to some level of precision) reported Network jack geocoding?
+*where do we persist this info
-*Would an additional open "Click to place/edit" or "drag and drop" interface over the facility image be useful let folks place themselves on the map let the community maintain the char?
-*When do we know where a new employee sits? Decided during paperwork processing or first day of work?
-*Are there "floater" employees in the office who just find an empty desk?
-=== Telecommuting Employees  ===
+<br>
-*Do we want their seat localtion For employees that have and office seat and regularly telecommute, do we want two(or more) seat locations? google maps (or similar service) for telecommuters, or even a precision fallback for any employee?
+==== Component III&nbsp;: Confluence of The above with the Moz phonebook  ====
-=== Contractors  ===
+*Seating chart location becomes an ldap field displayed on a phonebook record
+*clicking the link takes you to the floorplan image with emp's seat in focus
+*in on the "view the seating chart, we enable URI like this
-*is it useful to have this seat info info (at least to some precision&nbsp;: link to a google map)?
+&nbsp;&nbsp;&nbsp; .../seating/skeen@mozilla.com <br>&nbsp;&nbsp;&nbsp; we would not need to add any fields to Ldap
-*For contractors, I could definitely see an interface that allows the user to place themselves to be very useful.

Webdev/SeatingChart: Difference between revisions