My section is trying to force a switch to a new SharePoint with no folders, just a document repository with "enterprise key words"...
One of the places I worked . The IT department was a law unto itself.So can someone tell me if if if I'm being hacked?
Or are they just upgrading the system again ....
Back between 2006 and 2009 I was project director for a major JAG information management project. It was just as SharePoint 2007 was coming out. ADM(IM) were fairly reluctant at the time to let us use it but shortly came on board in a big way. Our objective, amongst other things was to get rid of the network shared drive systems (which were spread throughout the country and overseas and couldn't communicate with each other).
Back between 2006 and 2009 I was project director for a major JAG information management project. It was just as SharePoint 2007 was coming out. ADM(IM) were fairly reluctant at the time to let us use it but shortly came on board in a big way. Our objective, amongst other things was to get rid of the network shared drive systems (which were spread throughout the country and overseas and couldn't communicate with each other).
A shared network drive essentially is just a server whose hard drive(s) is(are) mapped to individual computers and allows people with access to store documents on the server rather than their local hard drive and thus make the files accessible to other people with permitted access. It's a simple system of file sharing with limited potential for growth and expansion or complexity.
SharePoint is a large toolset that can be widely deployed and has many purposes including document management. It's big advantage is that it's scalable and cloud based and highly configurable to allows you to build business applications on it which utilizes the data that the enterprise collects. Basically it allowed us to build a wide area cloud enterprise on a Protected B Windows Server backbone that allowed any one of our users to access the system from any DWAN computer or remote login to access their, their directorate or the whole system's files and applications. It allowed us to, amongst other things, set up a proper document and records management system that complied with Archives Canada's regulations as well as consolidate several dozen home-grown MS Access specialty databases into system-wide applications. It's also capable of doing case management and numerous other specialty workflow processes.
At the time we were roling it out I knew of only one other DND office that was using it but many that were turning to it. The result was we were constantly training new programmers who were being hired away by folks prepared to give them better pay. Any monkey can build a shared drive system. To build a proper SharePoint system takes talent but is worth it from a business applications point of view. What is absolutely critical when going to SharePoint is that a proper business analysis is done prior to building the system and a proper business transformation plan is in place to roll it out to the users.
Most people I come across in various workplaces hate SharePoint, mainly because they don't understand it I assume
View attachment 78051
should of had microsoft manage sharepoint for us, maybe then it would be more efficient
That's the trouble. Most people look at it as a high-end network storage system and build it to replicate what they are familiar with (all to often as paper and filing cabinet analogues - and don't even get me started on the DSCDS) .
Means "making a bit of code efficient before you're sure it's the particular code that needs to be made efficient". My jibe is that MS doesn't bother with "efficient" at all. Their business model has basically been to bet on a rough approximation of Moore's Law - in effect, that computing power would outstrip their profligate use of it.
I have no problem with it as a network storage system. The naval fleet schools, for example, teach the same courses but on different coasts. They should be using SharePoint as their every day repository for files (everything from QSPs, to lesson plans, to memo, to the plan for the Christmas party). They are not doing that, even though there is SharePoints for all these units (all these units are just ignoring and not using their SharePoints).
They went with RDIMS as the document management system for that. Which was a beast in and of itself.Back between 2006 and 2009 I was project director for a major JAG information management project. It was just as SharePoint 2007 was coming out. ADM(IM) were fairly reluctant at the time to let us use it but shortly came on board in a big way. Our objective, amongst other things was to get rid of the network shared drive systems (which were spread throughout the country and overseas and couldn't communicate with each other).
A shared network drive essentially is just a server whose hard drive(s) is(are) mapped to individual computers and allows people with access to store documents on the server rather than their local hard drive and thus make the files accessible to other people with permitted access. It's a simple system of file sharing with limited potential for growth and expansion or complexity.
SharePoint is a large toolset that can be widely deployed and has many purposes including document management. It's big advantage is that it's scalable and cloud based and highly configurable to allows you to build business applications on it which utilizes the data that the enterprise collects. Basically it allowed us to build a wide area cloud enterprise on a Protected B Windows Server backbone that allowed any one of our users to access the system from any DWAN computer or remote login to access their, their directorate or the whole system's files and applications. It allowed us to, amongst other things, set up a proper document and records management system that complied with Archives Canada's regulations as well as consolidate several dozen home-grown MS Access specialty databases into system-wide applications. It's also capable of doing case management and numerous other specialty workflow processes.
At the time we were roling it out I knew of only one other DND office that was using it but many that were turning to it. The result was we were constantly training new programmers who were being hired away by folks prepared to give them better pay. Any monkey can build a shared drive system. To build a proper SharePoint system takes talent but is worth it from a business applications point of view. What is absolutely critical when going to SharePoint is that a proper business analysis is done prior to building the system and a proper business transformation plan is in place to roll it out to the users.
I hate doing any kind of desk work in the military.
Yeah. We were forced into that by ADM(IM). We didn't want to and argued long and hard but in the end it is what it is. It wasn't only the fact that it was RDIMS but a version of RDIMS that was dated and already superseded by other better versions. But it was the one for which DND held all the licenses at that time. It caused a big problem with the case management solution which was required to integrate with RDIMS and in testing it didn't.
This was actually one of my frustrations in the JAG project.
