Discussions
Categories
Choose a Product
THRUST SERVICES
CORE APPS
CE PRODUCTS
...
Quick Links
POPULAR
HELPFUL TIPS
Groups
My Links
FOR SIGNED IN MEMBERS:
Back to website
Home
TeamSite
TeamSite, LiveSite and OpenDeploy
Multi-tagging and replicant management
Migrateduser
Currently our tagging file(s) implementation allows for only one tag to be set at a time and we'd like to multi-tag. The process to tag is to add a replicant and click the EDIT button which spawns a pop up window that the user can click from a list of tags. Once the tag is clicked the pop-up window closes after the replicant has accepted the values from the tag the user selected. In order to add another tag, a new replicant must be created and the EDIT button must be clicked to spawns the list of tags window again.
Is it possible add/remomve multiple replicants based on toggling the terms from a single pop-up window?
The use case would be the following: After file(s) selection for tagging, the Author would proceed with the current workflow of adding a replicant and clicking the EDIT button. Once the pop-up tag list window appears, the Author can toggle any number of tags and replicants will be created/removed in alignment. When tagging is completed, the Author closes the pop-up window and submits the tagging form.
We are using CGI_Lite and FormAPI manage the interactivity and data transfer to and from the replicants with XSL to manage the display of the popup.
Perhaps one of the biggest challenges of accessing the replicant container is that it is in one of four tabs of different tagging sections. We have area_path, iw_form_name, iw_callback_var, dctFieldSetType and iw_item_name already captured with cgi.
We do have a method that utilizes iw_form_name, traverses the DOM for matching values and populates the fields of the replicant used to launch the tag list pop-up window.
Can we further exploit iw_form_name to manage the creation/removal of replicants? If so, how? If not, then what do you suggest? Many thanks in advance.
Find more posts tagged with
Comments
There are no comments yet