nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Using Interwoven/TeamSite for Calendar of Events and Podcast Directory?

AllanS

It was proposed to the company I work for that we use Interwoven/TeamSite to handle part of a web site:
- A calendar of events (Ideally, we'd make calendar events available to other applications)
- A directory of podcasts

I am new to TeamSite, so I've been going over various documentation to find the best methodology to use to set this up.

Is anyone familiar enough with the documentation on how to accomplish this, or who is familiar with case studies? (I have read some of the basic documentaton but haven't yet found anything specifically related to events calendars or podcasts. From the looks of things, we may have to use OpenDeploy for this.) There does appear to be a lot of documentation; the problem I'm having is separating what's relevant to this case.

Thanks in advance.

Find more posts tagged with

Comments

gzevin

It was proposed to the company I work for that we use Interwoven/TeamSite to handle part of a web site:
- A calendar of events (Ideally, we'd make calendar events available to other applications)
- A directory of podcasts

I am new to TeamSite, so I've been going over various documentation to find the best methodology to use to set this up.

Is anyone familiar enough with the documentation on how to accomplish this, or who is familiar with case studies? (I have read some of the basic documentaton but haven't yet found anything specifically related to events calendars or podcasts. From the looks of things, we may have to use OpenDeploy for this.) There does appear to be a lot of documentation; the problem I'm having is separating what's relevant to this case.

Thanks in advance.

if you are new to TeamSite, I would suggest that you hire somebody just to go through the requirements and architect the solution.

I could offer some ideas (not sure you could use them though Smiley Very Happy

) - but they will depend on your requirements.

AllanS

if you are new to TeamSite, I would suggest that you hire somebody just to go through the requirements and architect the solution.

I could offer some ideas (not sure you could use them though ) - but they will depend on your requirements.

We may hire someone later on in the development process, but at this point we're still looking into basic feasibility. We don't need anything designed, we just need to know if we're on the right track using TeamSite to handle this.

nipper

Short answer, yes you can do this. Easy? Not quite.

1st point to remember is that TS is not a webserver. It is a content management tool. So it will not be the tool that delivers the podcasts or the event calender to the end user. TS will be a great help to users wanting to add/change/delete that content.

I worked on a project a couple years ago maintain the entertainment calendar for a family of casinos (gzevin was also on the project). The DCR was quite complex because there were scheduled acts (Joe plays for 5 days), there were permenant acts (Jean plays M,T,Th,F - but is off this week and a bunch of 1 off selections). That data was then pushed to a (very complex) RDBMS for a JSP server to dynamically serve the data.

Take Greg's point to heart, this needs to be designed very well in the beginning. Event calendars can get quite messy and you need to be able to handle the distinct variations.

HTH

Andy

AllanS

Short answer, yes you can do this. Easy? Not quite.

1st point to remember is that TS is not a webserver. It is a content management tool. So it will not be the tool that delivers the podcasts or the event calender to the end user. TS will be a great help to users wanting to add/change/delete that content.

Yeah, I have learned enough about TeamSite to know how its used in publishing (and, from our side of things, setting up a process for approving content).

I worked on a project a couple years ago maintain the entertainment calendar for a family of casinos (gzevin was also on the project). The DCR was quite complex because there were scheduled acts (Joe plays for 5 days), there were permenant acts (Jean plays M,T,Th,F - but is off this week and a bunch of 1 off selections). That data was then pushed to a (very complex) RDBMS for a JSP server to dynamically serve the data.

Just curious... if you had a separate server for handling schedule data, does that mean that the 'calendar' did not use the TeamSite facilities for editing and/or approving content for publishing? Or did the DB/Server generate the data that would then go through the TeamSite approval process?

Yes, I do know that eventually we'll probably need to bring in an expert to do a more complete design. But like I said, I just want to know what the capabilities of TeamSite are. (It is helpful to know that there's no built-in 'Calendar' and that however its designed, we'll have to do some custom work.)

nipper

Just curious... if you had a separate server for handling schedule data, does that mean that the 'calendar' did not use the TeamSite facilities for editing and/or approving content for publishing? Or did the DB/Server generate the data that would then go through the TeamSite approval process?

You will learn more about TS. However when you create a template (now called a form) it is stored as an XML file. That XML is what is edited, versioned, approved, etc by the end users. Once the data has been approved, it can be deployed to a RDBMS. Now, you could certainly push out an XML file only and have a php,jsp, some other page render the page on the fly.

If you want truly dynamic pages (this type of act, this date, this price range, etc) then you need a DB, either a full RDBMS, or an in-memory service that reads XML files.

If you want a static page that is the same for me as it is for you, then no DB is required.

TS will work in either scenerio