Logo 
Search:

Sharepoint Forum

 Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

learning project/organizational politics

  Asked By: Dominique    Date: Jun 14    Category: Sharepoint    Views: 908

If anyone out there is in the mood to share some of their Sharepoint
wisdom, I have some sort of vague, newbie-ish questions...

So a little background: I work on a research team that has been using
Sharepoint + custom databases as our primary means of project
management. We're coordinating a new project that will mostly be run
by people outside of our institute, and we're hoping to move more
project management functions online.

I don't know a whole lot about web development, but really want to
learn, so the idea is for this to be a learning project for me, and
hopefully for some stuff to be developed that could be useful on
future projects.

Problem is, I don't have much leeway to really get in there and make
changes and learn stuff. Our IT dept. doesn't want anyone to edit
pages with HTML editors, apparently because they worry about changes
made via FrontPage/Sharepoint Designer messing with pages throughout
the Sharepoint site hierarchy. I understand that FrontPage can be
unusually weird with extensions and whatnot, so I'm wondering if I
could make the case that using something like ASP.net wouldn't pose
the same problem (?)

Also, only members of the IT dept. are allowed access to the top
level site collections, so I can't create templates, can't upload add-
ons... which I can understand, but I'd *really* like to get in
there :-) I'm just wondering if there's some way, um... I don't
know, is there a way to establish a separate site hierarchy, that our
team would bear total responsibility for?

My research team is also considering just renting server space
ourselves so that we can develop our own Sharepoint hierarchy, but we
would like to find a way to work through our IT dept if possible.
The organizational politics of it all is a bit weird, since we're an
independent research team under a larger institutional umbrella.

But anyway... if you happen to have any thoughts, suggestions about
any of this, I would really appreciate it.

Share: 

 

4 Answers Found

 
Answer #1    Answered By: Judy Pittman     Answered On: Jun 14

I should add that we are using WSS2. Sorry for leaving that out.

 
Answer #2    Answered By: Caleb Gordon     Answered On: Jun 14

Your situation sounds common across a lot  of organisations.
The only way you would be able to get complete control over your hierarchy
would be to have your own site  collection. This would then give you the
flexibility you require. However be aware that using FrontPage (you would
have to as it is WSS v2) you could be given access  to just a team  site of
your own and make changes without affecting the rest of the sites. As long
as you had your own site which was not associated with anything else it
should be fine. I have worked on quite a few projects  where this is a
requirement and it is just as simple as giving the people  involved access to
a separate  site / site collection and leaving them to it. Now if you went
down the WSS v3 route then I would suggest the same as above but using
SharePoint designer  would give all the ASP.NET integration you may need. My
suggestion would be either get yourself a server  and build your own WSS
installation, or plead with the IT Dept to give you your own site
collection, in theory they should be happier with that idea  as you then
completely look after the site structure and they don't have to worry about
anything. If you break it oh well kind of thing. Anyway hope this helps in
some way.

 
Answer #3    Answered By: Irving Hurley     Answered On: Jun 14

So in talking with our IT folks, I had asked whether there was
a way we could get our own separate  hierarchy, so that our stuff
wouldn't affect anyone else, and they said that we would need to get
our own server  to do that. But maybe if I asked specifically for our
own "site collection," that would make more sense?

I'm just trying to figure out the right way to describe what we're
asking for, since I'm not sure that they themselves are aware of all
of Sharepoint's capabilities (?). Maybe the deal is that we can't
get our own "top level" site  collection without our own server, but
they could establish a new collection directly under the top level
for us, which would branch off from all the rest of the sites... if
that makes any sense...

"If you break it, oh well" is definitely what we're going for.

 
Answer #4    Answered By: Yvonne Rodriquez     Answered On: Jun 14

Here's the rundown on different levels of separation.

. A separate web  Application can be in its own App Pool. This means
that the website hosting sharepoint  has its own RAM and can't possibly
affect another Web Application running in a different App Pool

. Web Apps can host one site  collection in the root and several
other Site collections  on a managed path. A Site Collection is the basic
boundary for security. Groups and Permission Levels are defined at the Site
Collection level and inherit through the rest of the site. Your IT folk can
also delegate administration of Sharepoint by making you a Site Collection
owner without making you a sharepoint administrator.

. A top level site is always at the top of a Site Collection. The
Site Collection is actually administered using this top level site,
including security.

. Child sites inherit security from their parent site.

. Lists and Libraries inherit security from the site where they are
created.

. Items in a list/library inherit security from the list.

 
Didn't find what you were looking for? Find more on learning project/organizational politics Or get search suggestion and latest updates.





 
 
 
 

Related Post