Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Tagging Sites with Metadata

  Date: May 30    Category: Sharepoint    Views: 909

When we create new Site Collections we enter information about Site Owners, I
would like to be able to expand on this cabability by adding metadata fields so
that we could assign metadata to new site collections and possibly to subsites.
I'm envisioning assigning data such as department or site purpose or government
security level. Does anyone have any suggestions as to how this might be



5 Answers Found

Answer #1    Answered On: May 30    

1. When you create a new Site Collection you enter information about
the Site Collection administrators. This isn't the same thing as a Site
Owner. Site Owners have full control of the top level site of the site
collection (and inherit from there). But Site Collection Administrators
have control of the site collection itself. By default the site collection
admins are added to the Site Owners group.

2. Site Collections themselves don't have additional metadata fields.
I've seen people add something like metadata by creating a property bag
programmatically, but its not really the same thing as something like the
site description.

Having said that I have seen this kind of thing done by creating a custom
application page that asks for the additional information when the site
collection is created and then stores it in a property bag. But it requires
custom programming.

Answer #2    Answered On: May 30    

We've done it by having a list at the top level site collection of our web
app that houses the site collections we wanted to track. It did require
custom programming to create a custom form for people to fill out when
requesting a site collection. But, it wouldn't have had to, if we'd wanted
to give people direct access to the list.

Answer #3    Answered On: May 30    

Each site in SharePoint has a custom properties bag, custom
properties can be assigned programmatically. There is a codeplex application
which allows administrator to assign and view custom properties. Axceler
ControlPoint product allows you to assign and view custom properties and also
search sites based on their custom properties, along with many other things.

Answer #4    Answered On: May 30    

I would come at this from the front-end instead of filling out the data
you want after the fact. My thinking is that you create a list for
people's site requests that requires all of the metadata you are asking
for. That way when an admin goes to create the site you already have the
data you needed. The data is separate from the site, though. If you are
talking about displaying those metadata fields ON the site after it is
created then there are a number of possibilities:

1. Use web services (check out SPServices:
http://spservices.codeplex.com/) to do a lookup on your metadata list
and display the data in a <div id="divMetadata" /> on your site.
2. Use a workflow on that metadata list to automatically create your
site, though this may mean custom code. The data from the metadata list
could be passed along in the workflow to be displayed in the site
description placeholder. I may have seen a custom workflow activity on
iLoveSharePoint (http://www.ilovesharepoint.com) that creates sites
through SharePoint Designer workflows.
3. Perhaps a mix of the above along with some type of feature stapled
onto a custom site definition...definitely custom code. Also, suggestion of a property bag is certainly an approach I would
investigate if you are willing to go the custom code route.

Answer #5    Answered On: May 30    

For a "no code" solution...

Basic idea...
You could create a "special purpose"

- *list* or

- *folder* in an existing *list*

In the "special purpose" list / folder

- each *list item* is used to contain

- one or more of the metadata fields you require

In a bit more detail...
Build one or more *site template* to be used for each *top level site*

- incorporating the "special purpose" list / folder

- you can set permissions to restrict access

- you could also use a *content type* for each *list item*

You can then pick the*site template* to be used

- when you create a new *top level site* or

- even a new *site*

Hope this gives the basic idea

- many variations are possible on this theme

- for example - using the "special purpose" list/folder

- to manage changes to the *site collection* / *site*

- by having it contain change requests, etc...

Didn't find what you were looking for? Find more on Tagging Sites with Metadata Or get search suggestion and latest updates.