Re: OT - Using a Defect Tracking System to Create a Glossary

[Robert Lauriston]

What was the problem with Confluence?

Here's a new hosted service specifically for that purpose:
http://www.cloudwords.com/2012/08/cloudwords-takes-the-global-glossary-to-the-cloud/
___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

OT - Using a Defect Tracking System to Create a Glossary

[Robert Lauriston]

What was the problem with Confluence?

Here's a new hosted service specifically for that purpose:
http://www.cloudwords.com/2012/08/cloudwords-takes-the-global-glossary-to-the-cloud/

RE: OT - Using a Defect Tracking System to Create a Glossary

[David Artman]

I might be the only one confused... but what is the point of a defect
tracker to develop a glossary? Are you trying to use the tracker as a
means of handling review and edit? I mean... there's TONS of ways to
handle such a workflow, if the goal is merely:
* Someone comes up with a new term for the glossary, and defines it.
* The term and definition is shopped around various SMEs and interested
parties, for comments/edits.
* The term is added to some kind of FM file/book and the deliverable
(CHM file?) is re-generated and re-published.

Hell, it could be done with an Outlook task or an email chain; it could
be done on an internal, developmental wiki; it could be done in a
regular (e.g., weekly, monthly) meeting for all new term additions at
once.

I guess... uh, I guess I just don't understand why this is even a
question? Can you provide further details about tools limitations,
contributor requirements/restrictions, or other business needs that
might be impacting your choice of workflows, which is leading you to
reach out for advice...?
___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

OT - Using a Defect Tracking System to Create a Glossary

[Roopa Belur]

Hi All,

I have been assigned to create a comprehensive and a single glossary for 
documentation purposes. I am researching and evaluating several options at this 
time, and one of the suggestions i have received is to define a workflow (from 
Product Manager to Dev to Doc) using our defect tracking system.

We currently use Siebel to track defects. What are the pros and cons of using a 
defect tracking system to set up a workflow for a glossary? What are some of 
the concerns with this approach?

The eventual intent is to create a global file in Frame and use RoboHelp to 
make it available online to various groups within the company.

Please share your views when you have a minute.

Thanks for your help.

Rgds,
Roopa 
 
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.   

--H.H. the Dalai Lama___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

Re: OT - Using a Defect Tracking System to Create a Glossary

[Roopa Belur]

Thanks, David, for your response. I should have furnished more details, sorry 
about that.

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 read access to the others teams in the 
company.

 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.

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.

Rgds,
Roopa

 
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.   

--H.H. the Dalai Lama





 From: David Artman da...@davidartman.com
To: Roopa Belur rbe...@yahoo.com; Framers framers@lists.frameusers.com 
Sent: Friday, August 24, 2012 10:13 PM
Subject: RE: OT - Using a Defect Tracking System to Create a Glossary
 
I might be the only one confused... but what is the point of a defect
tracker to develop a glossary? Are you trying to use the tracker as a
means of handling review and edit? I mean... there's TONS of ways to
handle such a workflow, if the goal is merely:
* Someone comes up with a new term for the glossary, and defines it.
* The term and definition is shopped around various SMEs and interested
parties, for comments/edits.
* The term is added to some kind of FM file/book and the deliverable
(CHM file?) is re-generated and re-published.

Hell, it could be done with an Outlook task or an email chain; it could
be done on an internal, developmental wiki; it could be done in a
regular (e.g., weekly, monthly) meeting for all new term additions at
once.

I guess... uh, I guess I just don't understand why this is even a
question? Can you provide further details about tools limitations,
contributor requirements/restrictions, or other business needs that
might be impacting your choice of workflows, which is leading you to
reach out for advice...?___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

OT - Using a Defect Tracking System to Create a Glossary

[Roopa Belur]

Hi All,

I have been assigned to create a comprehensive and a single glossary for 
documentation purposes. I am researching and evaluating several options at this 
time, and one of the suggestions i have received is to define a workflow (from 
Product Manager to Dev to Doc) using our defect tracking system.

We currently use Siebel to track defects. What are the pros and cons of using a 
defect tracking system to set up a workflow for a glossary??What are some of 
the concerns with this approach?

The eventual intent is to create a global file in Frame and use RoboHelp to 
make it available online to various groups within the company.

Please share your views when you have a minute.

Thanks for your help.

Rgds,
Roopa?
?
"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."?? 

--H.H. the Dalai Lama
-- next part --
An HTML attachment was scrubbed...
URL: 

OT - Using a Defect Tracking System to Create a Glossary

[Roopa Belur]

Thanks, David, for your response. I should have furnished more details, sorry 
about that.

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 read access to the others teams in the 
company.

?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.

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.

Rgds,
Roopa

?
"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."?? 

--H.H. the Dalai Lama





 From: David Artman 
To: Roopa Belur ; Framers  
Sent: Friday, August 24, 2012 10:13 PM
Subject: RE: OT - Using a Defect Tracking System to Create a Glossary

I might be the only one confused... but what is the point of a defect
tracker to develop a glossary? Are you trying to use the tracker as a
means of handling review and edit? I mean... there's TONS of ways to
handle such a workflow, if the goal is merely:
* Someone comes up with a new term for the glossary, and defines it.
* The term and definition is shopped around various SMEs and interested
parties, for comments/edits.
* The term is added to some kind of FM file/book and the deliverable
(CHM file?) is re-generated and re-published.

Hell, it could be done with an Outlook task or an email chain; it could
be done on an internal, developmental wiki; it could be done in a
regular (e.g., weekly, monthly) meeting for all new term additions at
once.

I guess... uh, I guess I just don't understand why this is even a
question? Can you provide further details about tools limitations,
contributor requirements/restrictions, or other business needs that
might be impacting your choice of workflows, which is leading you to
reach out for advice...?
-- next part --
An HTML attachment was scrubbed...
URL: 

OT - Using a Defect Tracking System to Create a Glossary

[David Artman]

I might be the only one confused... but what is the point of a defect
tracker to develop a glossary? Are you trying to use the tracker as a
means of handling review and edit? I mean... there's TONS of ways to
handle such a workflow, if the goal is merely:
* Someone comes up with a new term for the glossary, and defines it.
* The term and definition is shopped around various SMEs and interested
parties, for comments/edits.
* The term is added to some kind of FM file/book and the deliverable
(CHM file?) is re-generated and re-published.

Hell, it could be done with an Outlook task or an email chain; it could
be done on an internal, developmental wiki; it could be done in a
regular (e.g., weekly, monthly) meeting for all new term additions at
once.

I guess... uh, I guess I just don't understand why this is even a
question? Can you provide further details about tools limitations,
contributor requirements/restrictions, or other business needs that
might be impacting your choice of workflows, which is leading you to
reach out for advice...?