Presentation given by Diane Montgomery of IT Services, University of Glasgow at the 'Managing Archaeology Data' event on Monday 7th March 2011 in Glasgow.
1. SharePoint Where we are and what’s happening next Diane Montgomery, IT Services March 2011
2.
3.
4.
5.
6.
7.
8.
9.
10.
Hinweis der Redaktion
To meet a set of requirements , based first 3 to portal - better access to existing IT services (ie without need to log on again). and collaboration tools for our STUDENTS . We are on Microsoft Office SharePoint server Enterprise version 2007 – and will be looking to upgrade to 2010.
At a high level, providing mysites and team sites. Both provide collaboration
Mysite gives a number of standard features - which you can change – and a getting started guide. Enlighten Library - moving to a Shibboleth/federated access login – later in the spring.
Team sites – areas of use? Emergent approach for local use– its a tool not solution – allowing a bottom up demand in the schools. (Quite a different feel to many of the key IT projects on the go at the moment in UoG.) IT helpdesk SP team deal enquires that come in. IT staff (school or college) need to support the running of a site collection and support their users . Good – understanding of local needs , Possible Cons – time.. Schools could divide into subject area or projects
Boiler plate templates Lists and Libraries Advantages over a J drive type acces Take your data management plan Use Lists to create meta-data – at site level perhaps different for documents and image libraries. Document Versioning and checkin -out is off by default, you can switch it on for each document library, so that might influence how you organise them. Document Workflows to collect feedback or approvals. Alerts settings – select set up on individual web parts to be notified if changes made and the type of changes, and instant, daily or weekly notification. Permissions for team members to securely access
Permissions are flexible and very much under the individual site owner control. Security trimming prevents seeing a site or webparts if you do not have access. Area of likely use in future would be audience targeting where you can mark up content to display only if someone is in an audiences, for example if you had a category final year ug the NSS survey announcement could be set to display only to them.
Lesson learned - the best use is where the purpose is clear, project or meetings based. Good thing about devolved to School IT to support site collection – is also a very bad thing as it depends what time they have to devote to it.