tag:blogger.com,1999:blog-6512742799532247661.post8641235688171095224..comments2023-03-16T08:05:11.958+00:00Comments on Records management futurewatch: Sharepoint: new technology; same issues?Steve Baileyhttp://www.blogger.com/profile/12352969237682900197noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-6512742799532247661.post-13578001120335611572011-05-19T15:33:35.288+01:002011-05-19T15:33:35.288+01:00I agree with you that MOSS seems to offer similar ...I agree with you that MOSS seems to offer similar solutions to EDRM. Seems strange that it's being presented as the best thing since sliced bread, but maybe there's more than meets the eye.records managementhttp://www.grmdocumentmanagement.com/noreply@blogger.comtag:blogger.com,1999:blog-6512742799532247661.post-8515181787204641532008-04-03T09:27:00.000+01:002008-04-03T09:27:00.000+01:00If an organisation is using SharePoint as a collab...If an organisation is using SharePoint as a collaborative tool, adding the records management function is an interesting proposition, as long as it meets functional requirements. It should be more cost effective than an EDRMS and has advantages from the user's perspective - staff are already used to how it looks and what it can do and are more likely to accept the change to records management. <BR/><BR/>The Defra case study referred to at the SharePoint Summit suggests keeping it really simple, using automatic record capture, so the user only has to identify whether the record is of low, medium or high importance. I do feel rather doubtful about this, especially as the system defaults to low. Steve, in your post of 31 March you seem to agree that in future we will see records retention determined by users.<BR/><BR/>SharePoint is versatile. It can link to external web content, making it available to other users. The person creating the link needs to consider whether the subject matter is appropriate (a case for issuing internal guidance on linking to Web2.0?) More needs to be done about email, of course.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6512742799532247661.post-40261047133409628502008-04-02T19:09:00.000+01:002008-04-02T19:09:00.000+01:00Steve, your observations chime with mine. While wo...Steve, your observations chime with mine. While working at the recently acquired TOWER Software, I helped gather requirements for our SharePoint/TRIM Context integration. Despite the new school/old school flavor of the two products, they seemed to do roughly same thing in largely similar ways. SharePoint fell right into the same traps that EDRM did, but hasn't yet developed the library of necessary implementation hacks needed to make it work in real-world implementations.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6512742799532247661.post-88453547712507960002008-04-02T16:32:00.000+01:002008-04-02T16:32:00.000+01:00Thanks for this. I think the point you make echoe...Thanks for this. <BR/><BR/>I think the point you make echoes some of the concerns that I picked up from what I heard - namely the apparent difficulty and cost involved in getting MOSS to integrate with other (non-MS) applications; and the lack of any constructive approaches to integrating MOSS with Web2.0 applications (by which I also meant hosted 'Office2.0' apps, such as the online WP packages you mention). <BR/><BR/>Your comments would seem to further suggest that these may well be valid concerns...Steve Baileyhttps://www.blogger.com/profile/12352969237682900197noreply@blogger.comtag:blogger.com,1999:blog-6512742799532247661.post-64698828869548085322008-04-02T16:17:00.000+01:002008-04-02T16:17:00.000+01:00One of the main problems with Sharepoint is its re...One of the main problems with Sharepoint is its reliance on Microsoft-only client technologies. Its sole out-of-the-box integration is with Office, with which it is tightly bound (hence "MOSS"). With the approval now of OOXML as an ISO standard, the authoring tool, be it Microsoft Word or OpenOffice (or any other) should now be an irrelevancy. Roll forward another few years and users may well have a different word processor at home as in the office, hosted on-line or on their mobile device(s), but still be able to author the same documents across all of these environments. Contrary to this, Microsoft's MOSS strategy provides a single stack straightjacket - which is great for Microsoft - but may not stand the test of time for organisations and users alike.Anonymousnoreply@blogger.com