[Buildingdata] Re: PlanOn

[Christopher Gutteridge]

At one point data.open.ac.uk were quite optimistic, but I don't know how 
far they got.

The issues at our end are mostly political. I've not gotten as far as 
anything so warm and cuddly as a technical problem, yet.

Right now every 6 months estates emails us a hand updated spreadsheet 
that they transcribe from Planon (sob). The advantage is that they do 
include the *reason* for deprecating an ID, and the do redact some 
things (Alien research hanger, moonbase etc). Reasons for redactions are 
things like sold (or no longer rent), demolished, merged, and my 
favourite; duplicate.

It bites us a bit that estates are OK with doing things like merging 35 
and 35A into just 35. This means that all 35A rooms also change ID, and 
lots of other departments (eg. timetabling) will not automatically 
adjust their keys to match.

If I was being a semantic purist, building URIs would be the ID number 
plus (if known) the year the ID was assigned. Of course, no body will be 
willing to look that stuff up just to say what building a vending 
machine is in. When they say the coke machine is in B35 that's good 
enough for their purposes :)

On 07/01/2014 11:14, Alexander Dutton wrote:
> Hi all,
>
> Is anyone managing to get automated feeds out of their PlanOn instances?
>
> Things we're starting to need out:
>
> * space data (identifiers, names, space type, etc)
> * space features from the facilities management component
>
> My initial enquiries here haven't been very encouraging (manual CSV
> reports), so I was hoping someone else is doing something cunning.
>
> Best regards,
>
> Alex
>

-- 
Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service: http://data.southampton.ac.uk/
You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/