Showing posts with label Site Collection Administrator. Show all posts
Showing posts with label Site Collection Administrator. Show all posts

Wednesday, November 13, 2013

Another Option for Business Users

So... you're a SharePoint power-user in your company, and let's say that you don't do programming, but you understand relational data models, queries, and application security models. What are your options for writing relational data-driven apps that you can publish to SharePoint? I was doing a freelance project for someone and it became obvious to me that my old stand-bys of InfoPath and custom lists with lookup columns just wasn't going to be enough. The data model was truly relational in nature and called for a little more of a heavy hitter.

Enter Access 2013 Web Apps... And a completely new experience.

It took a good textbook and a little time to catch on, but once I got the ball rolling, I was really able to make a truly mobile-friendly app that has a ton of functionality. Among the books that I purchased on this topic, here is the best one, in my opinion:


The application was easy to build, until I started using macros. Even then, the book I purchased (above) came in handy and I started getting more done. My client understood relational data models and eventually took over his own work on the project.

PROS:
1. Easy to build, once you figure out the navigation.
2. The data and all schemas are stored in SQL server and are able to be accessed and reported on by any SQL-compatible reporting / analysis tool.
3. The resulting application is EXTREMELY friendly to mobile browsers on both iOS and Android.
4. Includes several app templates to get you started.

CONS:
1. Little to no control over style sheets, which means...
2. No control over printer-friendly views.
3. Queries built in the application are read-only. I repeat: READ-ONLY. To replicate the functionality of UPDATE queries, data macros must be built with triggers to update existing records or create ancillary artifact records behind-the-scenes if you're not editing the active record on your screen.
4. I read somewhere that each app only has a 1 GB storage limit.
5. The only file type supported as a table field is an image file. You can try to upload any file type in an image field, but the web app will try to force it into an image file type. Not sure what the reasoning behind this is, especially when SQL supports just about any binary file type.

Overall, I like this product, but it is definitely in its infancy. It will need some work when it comes to ease of customizing security beyond the external SharePoint permissions, file types, and scalability. Be on the look-out for improvements in future versions of this application! It looks like Microsoft intends on putting quite an investment in re-inventing Access and using it to build effective cloud apps!

Wednesday, August 21, 2013

You Don't Have to Be a Weatherman To Know Which Way the Wind Blows.

Which direction is the wind blowing in terms of SharePoint?

Answer: JavaScript/JQuery (read "function") and CSS (Cascading Style Sheets, read "look and feel"), if you want to do anything above and beyond out-of-the-box with SharePoint 2010 and 2013.

With every new release of SharePoint, Microsoft is allowing SharePoint to be more flexible, but at the cost of becoming less user-friendly for non-developers. The newest release of SharePoint, SharePoint 2013, makes heavier use of "apps" that can be customized through script.

SharePoint Designer 2013 has taken away its Design view, and thrown the form customizations over the fence to InfoPath 2013.  InfoPath 2013 has some limitations, and so the most effective way to change the function of your SharePoint sites is to use JavaScript and JQuery. This means that even a Site Collection Administrator would be well-served to have knowledge of JavaScript, JQuery, and CSS.

Fortunately, there are many good books available on both subjects, and even books focused on using JavaScript, JQuery, and CSS within the context of SharePoint 2013. I would highly recommend also getting a book on the use of InfoPath 2013 and even Office 365, Microsoft's cloud-hosted SharePoint solution.

For an all-in-one book, I recommend "Pro SharePoint 2013 Branding and Responsive Web Development". "JavaScript and JQuery: The Missing Manual" is also a good read if you're starting anew with any type of development/programming and has good cross-references within.

Best of luck, and happy coding!

Wednesday, January 23, 2013

Definitions #3: Site Collection Administrator

The role of the SharePoint Site Collection Administrator (and equivalents listed below in the resume search terms section of this article) is to control all aspects of a Site Collection and all subsites, lists, and libraries contained therein. This person can control branding of a site collection, as well as layouts, master pages, style sheets, content types, site structure, content management, publishing of InfoPath forms (we'll cover InfoPath forms authors in another article), approval of submitted content, management of site columns, permissions, site collection search scopes, and creation of document libraries, lists, and associated workflows, both custom and out-of-the-box.

This role is one of the hardest to pinpoint and recruit. While no programming or previous administration skills are required, this skillset requires an immense amount of training, due to the massive number of features present in SharePoint. The Site Collection Administrator, of all the roles in SharePoint, is the one person who becomes intimately familiar with the out-of-the-box capabilities of SharePoint. This person is the power-user, and will usually also play the role of the business analyst within the scope of SharePoint.

Due to this familiarity with the application, the Site Collection Administrator also tends to become the first line of technical support and business analysis to the end users in the enterprise.  Sometimes this person is part of a small group that supports an entire enterprise, or this person is a point person for a particular business unit, with each business unit having one or two individuals responsible for administration of a SharePoint site collection. This person will build some of the closest connections / relationships possible in an entire enterprise and should also be very skilled at developing positive business relationships. A person who is good with both the technical and relational aspects is always worth their weight in gold.

The Site Collection Administrator is also responsible for learning how to use SharePoint Designer. SPD is used to edit style sheets, javascript, master pages, page layouts, (some) custom webparts, and custom rule-based workflows for automating business processes.

While not often recruited specifically, finding a person with a complete, robust skillset in Site Collection Administration can be very difficult to find. 

WARNING: the Site Collection Adminsitrator has the power to perform some devastating actions (most often times very inadvertently) that can take hours, days, and in rare cases, even WEEKS to overcome and restore. SENDING THIS PERSON TO TRAINING IS WORTH THE PRICE if they don't have previous experience.  A Site Collection Administrator can delete a list, library, subsite, and even their entire site collection. They can also put a custom workflow into an infinite loop. And, as I stated before, these actions usually happen completely by accident. Restoring deleted sites and site collections requires the intervention of the SharePoint Farm Administrator.

A note about Office 365 (O365, SharePoint Online, offered by Microsoft): Someone with Site Collection Admin experience is all you need to get started with using the SharePoint Online offerings through Microsoft. The highest level you will be allowed to administer is at the site collection level and provisioning site collections.

If a person is looking to become a full-time SharePoint professional, this is the place they should start, unless they are already .net programmer, in which case the person should look into becoming a SharePoint Developer.

Certainly, a SharePoint Administrator or SharePoint Developer could be very well-versed on Site Collection Administrator skills, but many times the SharePoint Admins are Windows Systems Engineers and SharePoint Developers are .net cross-trainees, and neither of these ever really get experience solving business problems with out-of-the-box SharePoint solutions like the true Site Collection Administrator does. Please keep this in mind when evaluating the value (read "salary") of an experienced Site Collection Administrator.

Key Recruiter Take-Aways: An experienced SharePoint Site Collection Administrator is worth their weight in gold to the customer you place them with... be prepared to pay the piper. The experience that an experienced SCA has takes YEARS to accumulate and is constantly evolving. While a degree in Computer Science isn't necessary, a solid understanding of prepositional (boolean) logic is necessary to properly leverage things like custom views and filtering, and make modifications to pages that leverage javascript and other function calls. And finally, as mentioned in a previous post, an experienced Site Collection Administrator can and should strive to learn the back-end of SharePoint Administration. It is the next step in the natural career progression in the SharePoint ranks. If you are confident that a person can make the transition and they REALLY want to make the transition, you may be able to hire a trainable SharePoint Administrator at a discount if they have the necessary Site Collection Administrator experience.

Resume Search Terms: SharePoint Site Collection Administrator, SharePoint Analyst, SharePoint Business Analyst, SharePoint Specialist, SharePoint Designer (the tool, not the job title... we will cover the job title of SharePoint Designer later), SharePoint Knowledge Manager, SharePoint Content Administrator, SharePoint Content Manager, SharePoint Permissions, SharePoint Administrator (optional), SharePoint Application Administrator (optional).