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; } } }

File relationship in Teamsite

helloworld

Have worked on the Teamsite Content Center for a period, many questions have raised in my mind.
The Teamsite Content Center is a content management system, but I found it lack of many management level features.
e.g.
1. The files that have been imported into teamsite, they are existed independently. If we have a word document and it has another attachment word document, how can we build a relationship in both? (may be can use metadata to indicate, but it is very implicit)
2. After some days, the attachment is out of date and need to be deleted. When we deleted the attachment, how can we know that whose files that was relating to it?

May be I still not know teamsite well, if I have mistake, please advise me.And, if you have good approaches about those question, please share with us. Thank you !

Find more posts tagged with

Comments

Sailesh

Have worked on the Teamsite Content Center for a period, many questions have raised in my mind.
The Teamsite Content Center is a content management system, but I found it lack of many management level features.
e.g.
1. The files that have been imported into teamsite, they are existed independently. If we have a word document and it has another attachment word document, how can we build a relationship in both? (may be can use metadata to indicate, but it is very implicit)
2. After some days, the attachment is out of date and need to be deleted. When we deleted the attachment, how can we know that whose files that was relating to it?

May be I still not know teamsite well, if I have mistake, please advise me.And, if you have good approaches about those question, please share with us. Thank you !

How can a Content Management System Identity which document is linked to which document, may be there is something which may be there in a Document management system but since Teamsite is a web Content management system, I don't think these kind of features make sense.

kaalraa

Have worked on the Teamsite Content Center for a period, many questions have raised in my mind.
The Teamsite Content Center is a content management system, but I found it lack of many management level features.
e.g.
1. The files that have been imported into teamsite, they are existed independently. If we have a word document and it has another attachment word document, how can we build a relationship in both? (may be can use metadata to indicate, but it is very implicit)
2. After some days, the attachment is out of date and need to be deleted. When we deleted the attachment, how can we know that whose files that was relating to it?

May be I still not know teamsite well, if I have mistake, please advise me.And, if you have good approaches about those question, please share with us. Thank you !

You are looking out the features of Document Management from a tool which is better known for its content management and thats too on the web. Smiley Happy

iw_store

Have worked on the Teamsite Content Center for a period, many questions have raised in my mind.
The Teamsite Content Center is a content management system, but I found it lack of many management level features.
e.g.
1. The files that have been imported into teamsite, they are existed independently. If we have a word document and it has another attachment word document, how can we build a relationship in both? (may be can use metadata to indicate, but it is very implicit)
2. After some days, the attachment is out of date and need to be deleted. When we deleted the attachment, how can we know that whose files that was relating to it?

May be I still not know teamsite well, if I have mistake, please advise me.And, if you have good approaches about those question, please share with us. Thank you !

I feel IW, not only for managing webcontent, it has other facility too. It's support for webcontent mgmt is superub. But Questions like above good to put in discussion forum.

Migrateduser

You are looking out the features of Document Management from a tool which is better known for its content management and thats too on the web.

Could you share more about the differences between Document Management and content management.

1. The files that have been imported into teamsite, they are existed independently. If we have a word document and it has another attachment word document, how can we build a relationship in both? (may be can use metadata to indicate, but it is very implicit)
2. After some days, the attachment is out of date and need to be deleted. When we deleted the attachment, how can we know that whose files that was relating to it?

This is still true for web content like images, javascript, media files ... when the documents are imported into the repository using the interface. The only way I know is to associate metadata i.e extended attributes to the files after importing. Purging or deleting not required files is a very difficult unless there is a way to mark the files as zombie and clean up regularly.

dd_form.pdf

ccprofessional

Guys, don't mean to be rude but how about checking your spellings and grammar before you post?

Regarding the first post, What are EAs for?
Between metadata, workflows and Templating, you can pretty much do whatever you want.

kaalraa

Could you share more about the differences between Document Management and content management. .

In basic terms Content is for textual data whereas document is to refer a complete doc such word files, excel files, pdf files etc.

This is still true for web content like images, javascript, media files ... when the documents are imported into the repository using the interface. The only way I know is to associate metadata i.e extended attributes to the files after importing. Purging or deleting not required files is a very difficult unless there is a way to mark the files as zombie and clean up regularly.

I have never quoted those words.

Adam Stoller

The only relationships that TeamSite comprehends out-of-the-box is between DCT -> DCR -> PT -> generated page - and yes, that is done via TeamSite extended attributes (EAs).

For any other associations you would probably have to use custom EAs and custom scripts to manage / maintain / verify those associations that you wish to keep.

Perhaps as Interwoven continues to try to provide interfaces between their various products you might be able to do something with a TeamSite-to-WorkSite interface.

(note: Interwoven used to have a product called TeamXML which tracked relationships between various XML component pieces - but I believe that product is no longer supported)

jkm

These features are not available as part of the base TS product but TS provides high amount of flexibility to customize the things as per customer needs.

This can be achieved using EAs and as you have already said using metadata.

RonaldV

Hi Seagate,

you are right, the functions you are looking for (what I would call 'Referential integrity', what files refer to which files?) is missing in TS. This is due to the architecture which is 100% file based and not database-based (like many other CMS's). Both methods have their advantages.

What most organisations that require your requested functionality do is build-up & maintain their own database that contain the inter-file-relationships.

What you need for this (all custom build) is:
- a database with tables etc.
- a script that updates the database (either a nightly batch or something workflow-included)
- a script that will retrieve & show the data (from the db to the user)

What is crucial for this approach is that your relationship data can be easily read from the files, e.g. your files must be well structured and contain the required relationship-data. I guess that an attachment in word does not meet this requirement.

Hope this helps, ROnald

helloworld

Hi ccprofessional,
I am sorry that I am not good at english, because my first language is not english nor latin language family.

helloworld

Thanks for all your answers, yes, as you said we can build our customized module out of the teamsite, it is the current approach.
But as a customer of Teamsite, we hope Teamsite could owned the feature in the future.

Ninerfan

I've had the same concern dating back many years when I was first introduced to TeamSite 4.2.1. The core architecture has not changed so the same problem exists today. I worked on one implementation of TeamSite where a very senior IW consultant spent about two months building workflow to handle the delete of files and a related database that held all the relationship information about files and links. Let me tell you it was extremely complex and in the end did work but was sort of klunky to use and difficult to keep working. It was a real beast. I personally like to use cheap 3rd party software to understand page and link relationships. For example you can have workflow tied to a delete action that goes to a few folks who have access to the software. They can then determine the impact of the delete action and act accordingly BEFORE doing the delete. I've seen this method used a few places. It's easy to support and cheap to implement! Here is the software tool I've used in the past. Web Link Validator by Rel Software.
http://www.relsoftware.com/

Cheers!

ISCBorisB

Here is the software tool I've used in the past. Web Link Validator by Rel Software.
http://www.relsoftware.com/Cheers!

There are several *Link Validators* on the market, commercial and freeware both. Please note however that the whole thread
was started with the *Office to Office* attachment issue.

There are Document Management systems that will automatically maintain this information for you but no Link Crawler would.
It also breaks completely on custom link syntax like JS functions, custom ASP/JSP Tags, *dynamic* Pages like CGI and on and on...