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

How to store list of content items?

Binettoid

Hi guys,
I am trying to allow my users to create a list of content from the content stored within my TS (7.1) website and save/export/print this content in one click.
What's the best way to approach this?
Any suggestions appreciated.

Find more posts tagged with

Comments

curiousmaverick

I fail to understand your requirement here.

You mean list of DCRs/generated files? These are lready saved. So can't really figure out what you want to save.

You need to elaborate more.

Adam Stoller

I don't completely understand what you're trying to do either - however, since CCStd doesn't tend to provide checkboxes for selecting files (like CCPro does) I'm not sure if you'll be able to accomplish what I think you're trying to do - though since I'm not sure what that is, I could be wrong...

Binettoid

Hi thanks for your replies, I realise this was a bit vague.
My users will be viewing content on the final website and want to use a shopping-cart-like approach to create a collection of items. These items may be DCRs and generated pages (static HTML) or even PDFs. I want site visitors to be able to save these collections (adding a title, description, etc.) and email/print the collection out in one click. They also need to be able to come back and retrieve these collections, for example by title.
Any ideas appreciated!

new_report_1.rptdesign

table_export.xlsx

Adam Stoller

Hi thanks for your replies, I realise this was a bit vague.
My users will be viewing content on the final website and want to use a shopping-cart-like approach to create a collection of items. These items may be DCRs and generated pages (static HTML) or even PDFs. I want site visitors to be able to save these collections (adding a title, description, etc.) and email/print the collection out in one click. They also need to be able to come back and retrieve these collections, for example by title.
Any ideas appreciated!

So you're talking about a front-end application / interface - not a TeamSite (back-end) application / interface?

Binettoid

Yes ghoti, that's correct.

Adam Stoller

My guess is that you'll have to embed a lot of extra information into your web pages including some form of application (javascript?) that allows them to store the information associated with the content, image, etc. in a cookie or some such, and then provide an interface that can then retrieve the information from the cookie and process it somehow.

Keep in mind that if you're doing this with javascript that you will probably need some server-side scripting as well in order for the front-end to talk to the back-end (TS) to do what it sounds like you are trying to do.

Is this reasonable? No idea - it sounds a bit convoluted to me, but then I'm not involved with your project.

Binettoid

You mean to say that nobody has ever attempted to implement a shopping cart or similar functionality in a TeamSite-based system?
Hey I know this is not the typical/intended use or exactly what TeamSite is aimed at, but at the same time, this isn't rocket-surgery! Hasn't anyone done something like this? A few pointers about how to architect this type of thing would be most appreciated, or if some of you TeamSite gurus could just outline some pros and cons of a given approach, your wisdom would be most appreciated.

Adam Stoller

You mean to say that nobody has ever attempted to implement a shopping cart or similar functionality in a TeamSite-based system?
Hey I know this is not the typical/intended use or exactly what TeamSite is aimed at, but at the same time, this isn't rocket-surgery! Hasn't anyone done something like this? A few pointers about how to architect this type of thing would be most appreciated, or if some of you TeamSite gurus could just outline some pros and cons of a given approach, your wisdom would be most appreciated.

Shopping carts are generally front-end applications associated with a database. You seem to be suggesting that you want some sort of front-end application associated with a back-end application (TeamSite) - I doubt many implementers have had to do something like this.
I would imagine, though, that if you are using DataDeploy (or similar) to push information about the files into a database from TeamSite that you may be able to use something akin to the "standard" shopping cart implementation to reference that database from the front-end and thus provide a trail back to the actual TeamSite assets.

If you don't know anything about implementing a shopping-cart (I don't - I'm just making semi-educated guesses here) - then you probably need to look elsewhere for examples of how to code one.

nipper

You may want to table this for a few months. TeamSite 7.2 is due to be released soon and will have some functionality that will make this an easier thing to do.

I have implemented change sets in TeamSite before. It is not trivial and required a lot of custom code. TS 7.2 now has associations between disparate objects that will make this much easier to do.

Andy