<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt"><div><span>Thanks, David, for your response. I should have furnished more details, sorry about that.</span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: arial, helvetica, sans-serif; background-color: transparent; font-style: normal; "><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: arial, helvetica, sans-serif; background-color: transparent; "><span>The localization team in our company does use a legacy in-house system to add, review and edit terms and definitions to the "localized" glossary. This process has proved to be efficient and self-sufficient, however, it requires a considerable amount of developmental effort to replicate the same process and workflow for our (documentation) project. Our intent is to create a global file of terms and definitions and provide a <span
style="font-style: italic;">read</span> access to the others teams in the company.</span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: arial, helvetica, sans-serif; background-color: transparent; font-style: normal; "><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: arial, helvetica, sans-serif; background-color: transparent; font-style: normal; "><span> We have evaluated Wiki and Confluence as well, and it does not appear to fulfill our needs. We are talking at least 3000 to 4000 terms and definitions here.</span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: arial, helvetica, sans-serif; background-color: transparent; font-style: normal; "><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: arial, helvetica, sans-serif; background-color: transparent; font-style: normal; ">Siebel was suggested to us, and I was wondering if anyone has
used a defect tracking tool for glossary purposes before. Siebel is primarily a CRM tool, so am trying to understand better how we could use it to build a database of glossary terms and definitions.</div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: arial, helvetica, sans-serif; background-color: transparent; font-style: normal; "><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: arial, helvetica, sans-serif; background-color: transparent; font-style: normal; "><span>Rgds,</span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: arial, helvetica, sans-serif; background-color: transparent; font-style: normal; "><span>Roopa</span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: arial, helvetica, sans-serif; background-color: transparent; font-style: normal; "><br></div><div> </div><div><div><div><div id="0"> </div><div class="MsoNormal" style="MARGIN:0in 0in
0pt;"><span style="color: navy; font-family: 'Monotype Corsiva'; "> </span><span style="font-size: 12pt; color: rgb(51, 51, 0); font-family: 'Times New Roman'; "><b><font face="Tahoma" color="#666666" size="2">"This is my simple religion. There is no need for temples; no need for complicated philosophy. Our own brain, our own heart is our temple; the philosophy is kindness." <br><br>--H.H. the Dalai Lama</font></b></span></div><br><br><span id="hbblock"> <div> <div><font size="1"></font></div></div></span></div></div></div><div><br></div> <div style="font-family: arial, helvetica, sans-serif; font-size: 10pt; "> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> David Artman <david@davidartman.com><br> <b><span style="font-weight: bold;">To:</span></b> Roopa
Belur <rbelur@yahoo.com>; Framers <framers@lists.frameusers.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Friday, August 24, 2012 10:13 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> RE: OT - Using a Defect Tracking System to Create a Glossary<br> </font> </div> <br>
I might be the only one confused... but what is the point of a defect<br>tracker to develop a glossary? Are you trying to use the tracker as a<br>means of handling review and edit? I mean... there's TONS of ways to<br>handle such a workflow, if the goal is merely:<br>* Someone comes up with a new term for the glossary, and defines it.<br>* The term and definition is shopped around various SMEs and interested<br>parties, for comments/edits.<br>* The term is added to some kind of FM file/book and the deliverable<br>(CHM file?) is re-generated and re-published.<br><br>Hell, it could be done with an Outlook task or an email chain; it could<br>be done on an internal, developmental wiki; it could be done in a<br>regular (e.g., weekly, monthly) meeting for all new term additions at<br>once.<br><br>I guess... uh, I guess I just don't understand why this is even a<br>question? Can you provide further details about tools limitations,<br>contributor
requirements/restrictions, or other business needs that<br>might be impacting your choice of workflows, which is leading you to<br>reach out for advice...?<br><br><br> </div> </div> </div></body></html>