10 likes | 99 Views
Showing the Way in SharePoint: What Every Librarian Should Know. Portal Development Process. Planning for a Portal.
E N D
Showing the Way in SharePoint: What Every Librarian Should Know Portal Development Process Planning for a Portal Many life sciences organizations have deployed Microsoft Office SharePoint Server-based collaborative portals for communication and data sharing. A collaborative portal can streamline the management of distributed scientific research. However, getting beyond the basics and using out-of-the-box features of this powerful software can be overwhelming. Following a planning and development process grounded in information services competencies can help information professionals build and support portals that are sustainable and usable collaborative research spaces. An Information Specialist leads the development of an effective information space by combining knowledge of the organization and project with expertise in information services, tools and technologies. Which technologies match the project and participants? Start with a set of simple questions about collaborative work, communication, artifact organization and recall, and tracking activities to ascertain your user’ Collaborative Work What are the structure and culture of your collaboration? Communication What requirements or goals exist for dissemination of information? * Announcements * Revision notes * Discussion board * Decision recording * E-mail * Wikis * Relationships * Locations * Participant roles * Meetings * Contacts * Cultural preferences Why Portals? • The overhead of collaboration is reduced by spreading the burden over entire set of participants • Information resides in a centralized repository • A shared workspace builds community and trust • Contributing gives participants a sense of ownership of the collaboration output and fosters greater dedication • Tracking and recording of assets and artifacts is simpler and becomes a group responsibility Artifact Organization and Recall Tracking Activities What needs to be tracked or recorded and in what format? What are the products of your work? * Calendar events * MTAs * Approval records * Reports * Shipping records * Milestones * Project management * Tasks * Presentations * Images * Publications * Wikis * Documents * Posters Wiki Pages and List Features Data Review Workspaces Collaborative Databases • Use for sharing complex sets of data and previewing relevant sets • Metadata provides category filters to drive views for users • Versioning captures changes for each recordc • Use for virtual review of data analysis by collaborators • Transparent, private access to reviewers only increases trust • Context-rich environment brings project pieces together • Create a wiki using basic wiki markup and HTML • All wiki pages are stored a list items; manage items in bulk • Topic selection supports presentation of similar items • Use for sharing complex sets of data and previewing relevant sets • Metadata provides category filters to drive views for users • Versioning captures changes for each record Insert URL and description for embedded navigation Select topic Clear review instructions Discussion link User transparency Documents for review Show or hide fields