Difference between revisions of "CNMCyber transcript"

From CNM Wiki
Jump to: navigation, search
(→‎Steps to create a script)
(→‎Transcription Tasks)
 
(62 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
==Script Development for CNMCyber Events==
+
[[CNMCyber transcript]] is technically wording which is used in [[CNMCyber Office Hours]] events. In the best case scenario, it should be typed and moved to the requirements.
  
−
===What is a script===
+
The transcript can also be defined as the record of someone's requirement.  
−
:Script is technically wording which is used in [[CNMCyber Office Hours]] events. In the best case scenario, it should be typed and moved to the requirements.  
 
  
−
:The script can also be defined as the record of someone's requirement.  
+
The transcript is also an intermediate product, it's not a final product. It's a deliverable but is not user deliverable. It's a sub-product. So then when the transcript is available, a wikipage can be developed from the requirements in the transcript.
  
−
:A script is also an intermediate product, it's not a final product. It's a deliverable but is not user deliverable. It's a sub-product. So then when a script is available, a Wiki page can be developed from the requirements in the script.
 
  
−
===Purpose and Importance of Scripting===
+
==Transcript Development for CNMCyber Events==
 +
 
 +
===Purpose and Importance of Transcription===
 
:*To have a written record of requirements discussed during the event.
 
:*To have a written record of requirements discussed during the event.
−
:*Support traceability between event discussions and final wiki pages. The script itself leads to requirements. The script isn't the final product, but the requirements that a customer agrees to become the actual product. This can be measured, and in the best situation, it should be a [[requirements traceability matrix]] ([[requirements traceability matrix|RTM]]) record.
+
:*Support traceability between event discussions and final wiki pages. The transcript itself leads to requirements. The transcript isn't the final product, but the requirements that a customer agrees to become the actual product. This can be measured, and in the best situation, it should be a [[requirements traceability matrix]] ([[requirements traceability matrix|RTM]]) record.
  
 
:For example, when you write down requirements on a page, imagine it's what you're presenting to your boss or customer. You're saying, "This is what you'll get." You list down everything – like having HumHub, Odoo, Jitsi set up in a certain way, using ProxmoxVE, making it highly available with three nodes, having a public IPv4 network, running on Apache and Nginx, using Ceph for storage, and routing with [[pfSense]]. You ask, "Is this what you want?" They either sign or confirm via email. This becomes a kind of blueprint.
 
:For example, when you write down requirements on a page, imagine it's what you're presenting to your boss or customer. You're saying, "This is what you'll get." You list down everything – like having HumHub, Odoo, Jitsi set up in a certain way, using ProxmoxVE, making it highly available with three nodes, having a public IPv4 network, running on Apache and Nginx, using Ceph for storage, and routing with [[pfSense]]. You ask, "Is this what you want?" They either sign or confirm via email. This becomes a kind of blueprint.
  
−
===Components of a script===
+
===Components of a transcript===
−
:A script should focus on important information, omitting irrelevant details. A script should omit things like;  
+
:A transcript should focus on important information, omitting irrelevant details. A transcript should omit things like;  
  
 
:*"my name is _ _ _"  
 
:*"my name is _ _ _"  
Line 22: Line 22:
 
:*"I will answer another call."  
 
:*"I will answer another call."  
  
−
:It's not important. So script should include what is important, what should be and what can be moved to requirements.
+
:It's not important. So a transcript should include what is important, what should be and what can be moved to requirements.
  
−
===Scripting for CNMCyber Events===
+
===Transcription for CNMCyber Events===
−
:Scripts will be developed on wiki project page (currently - discussion page) of the product page. The main page is the product and discussion will be a project. Project (current discussion page), here there will be information how the product was developed and what requirements were involved.
+
:Transcripts will be developed on wiki project page (currently - discussion page) of the product page. The main page is the product and discussion will be a project. Project (current discussion page), here there will be information how the product was developed and what requirements were involved.
  
 
===Target Audience and Deliverables===
 
===Target Audience and Deliverables===
−
:A developer working on the product is the target audience of the script. Script by itself is the intermediate product, the product page is the end product and script is a part of development with a deliverable.
+
:A developer working on the product is the target audience of the transcript. Transcript by itself is the intermediate product, the product page is the end product and transcript is a part of development with a deliverable.
  
 
===Success Criteria and Desired Outcome===
 
===Success Criteria and Desired Outcome===
−
:Success for a script is determined by how useful it is. The goal is having Wiki Pages that describe products. For example; we need to have this platform on which our Jitsi will work, which is called talk and we will do this conference one day on the Talk.cnmcyber.com slash something - So right now we are doing this on employableU which is temporary. So the end product is the service but to build this firm we need to have a description of what we are doing, what we need to look for, and what we need to do. So now, in this case the desired out come is a  working technology.
+
:Success for a transcript is determined by how useful it is. The goal is having Wiki Pages that describe products. For example; we need to have this platform on which our Jitsi will work, which is called talk and we will do this conference one day on the Talk.cnmcyber.com slash something - So right now we are doing this on employableU which is temporary. So the end product is the service but to build this firm we need to have a description of what we are doing, what we need to look for, and what we need to do. So now, in this case the desired out come is a  working technology.
  
−
:The technical sense, quality is confirmation the description of the product matches the product itself right. So we have requirements and we have a product. If there's gaps, it's a quality product. But to know that you have a quality product you need to have a description, if you don't have a description how would you know? Scripting is a good way to build this description.
+
:The technical sense, quality is confirmation the description of the product matches the product itself right. So we have requirements and we have a product. If there's gaps, it's a quality product. But to know that you have a quality product you need to have a description, if you don't have a description how would you know? Transcription is a good way to build this description.
  
−
===How to claim a Scripting task===
+
===How to claim a transcription task===
−
:If you are a contractor developing scripts for [[CNMCyber Office Hours]] you will need to;
+
:If you are a contractor developing transcripts for [[CNMCyber Office Hours]] you will need to;
−
:#Go to [[Talk:CNMCyber_script]] to access the scripting tasks list
+
:#Go to [[Talk:CNMCyber transcript]] to access the transcription tasks list
−
:#Find the title of the task you would like to create a script for
+
:#Find the title of the task you would like to create a transcript for
−
:#In the "Contractor" column on the row for that task, write your name to indicate you will be responsible for this script
+
:#In the "Contractor" column on the row for that task, write your name to indicate you will be responsible for this transcript
−
:#In the "Due Date" column on the same row, enter the date when you expect the script to be completed
+
:#In the "Due Date" column on the same row, enter the date when you expect the transcript to be completed
 
:#Notify your CNMCyber contact when you have claimed a task so they know it is assigned
 
:#Notify your CNMCyber contact when you have claimed a task so they know it is assigned
−
:#Develop the script according to the description requirements best described on this wiki page
+
:#Develop the transcript according to the description requirements best described on this wiki page
 
:#Once complete, notify your CNMCyber contact person.
 
:#Once complete, notify your CNMCyber contact person.
 
:#If you have any questions about the task, get clarification from your CNMCyber contact before claiming and beginning work.
 
:#If you have any questions about the task, get clarification from your CNMCyber contact before claiming and beginning work.
  
−
===Steps to create a script===
+
===Steps to create a transcript===
−
:#Transcribe the audio - This can be done manually by listening and typing or if the event is posted on YouTube Channel you can extract the transcript by clicking on the three dots at the bottom right of the video and select show transcript. A side bar will be displayed with the transcript and time stamps. Highlight the entire transcript then copy and paste to the page where you will create the script from.   
+
:#Transcribe the audio - This can be done manually by listening and typing or if the event is posted on YouTube Channel you can extract the transcript by clicking on the three dots at the bottom right of the video and select show transcript. A side bar will be displayed with the transcript and time stamps. Highlight the entire transcript then copy and paste to the page where you will create the transcript from.   
−
:#Clean up the transcript - correct any mistakes in the transcription, eliminate timestamps, and filler words such as "um," "hmm," "oh," "like," "you know," "so", as well as any unnecessary side conversations or interruptions that shouldn't be in the final script. Also remove any repetitions.  
+
:#Clean up the transcript - correct any mistakes in the transcription, eliminate timestamps, and filler words such as "um," "hmm," "oh," "like," "you know," "so", as well as any unnecessary side conversations or interruptions that shouldn't be in the final transcript. Also remove any repetitions.  
 
:#Structure the information - Break the transcript into logical sections using headers. For example, you may have a section for Introduction, topics that were discussed in the meeting
 
:#Structure the information - Break the transcript into logical sections using headers. For example, you may have a section for Introduction, topics that were discussed in the meeting
−
:#Focus on key points - Summarize the script while paying attention to key questions, decisions, and discussion points that are relevant for the requirements of the product.   
+
:#Focus on key points - Summarize the transcript while paying attention to key questions, decisions, and discussion points that are relevant for the requirements of the product.   
−
:#Review the scrip - Go over the draft script and make any final edits to improve clarity. The goal is to create a traceable record of the event that can used to create product requirements.
+
:#Review the scrip - Go over the draft transcript and make any final edits to improve clarity. The goal is to create a traceable record of the event that can used to create product requirements.
−
:#Stick to the requirements - Make sure the script contains the information needed for the product requirements.
+
:#Stick to the requirements - Make sure the transcript contains the information needed for the product requirements.
−
:#Add attributions - Note who said what using speaker attributions like "Kevin:"
+
:#Add attributions - Note who said what using speaker attributions like "Kevin:".
 +
:#Add attribute questions - Note who asked each question using "[Name] asked:".
 +
:#Add attribute answers - Indicate who provided each answer using "[Name] answered:".
 
:#Check accuracy - Verify names, titles, terminology, and facts.
 
:#Check accuracy - Verify names, titles, terminology, and facts.
−
:#Save the script - Save the script to the discussion page (project page) of the product being developed.
+
:#Save the transcript - Save the transcript to the discussion page (project page) of the product being developed.
−
:#Ask clarifying questions - Get any needed context before beginning to create the script.
+
:#Ask clarifying questions - Get any needed context before beginning to create the transcript.
−
 
 
−
==Turn around time==
 
−
:When following the steps to claim a scripting task from the scripts list, contractors should set the due date in Step 4 to reflect completion of the script within a maximum of two days or less from the date the scripting task was claimed. After accessing the scripts list in Step 1, locating the desired task in Step 2, entering your name in the "Contractor" column in Step 3, and indicating the due date in Step 4, the claimed script development should then be finished within the due date indicated.
 
−
 
 
−
===Contractor Agreement===
 
−
This [[Careerprise contractor agreement]] (hereinafter, the ''Agreement'') is made and entered into as of ____________________ ''[Month, Day]'', 2023 (hereinafter, the ''Effective Date'') between [[Virginia Institute of Technology]] (hereinafter, the ''Company''), a Virginia [[limited liability company]], and ____________________ ____________________ ''[[[Careerprise contractor]]'s name]'', a ____________________ ''[State and business type, if different from a self-employed]'' (hereinafter, the ''Contractor''; both collectively, the ''Parties''; separately, ''Party'').
 
−
 
 
−
The ''Parties'' therefore agree as follows:
 
−
*The ''Company'' may request the ''Contractor'' to perform scripting services (hereinafter, the ''Services'') for the ''Company'' and, if so, promises to compensate the ''Contractor''; and
 
−
*The ''Contractor'' shall either reject the ''Company''<nowiki>'</nowiki>s offers or perform the requested services; and
 
−
In their actions or lack of actions under that ''Agreement'', the ''Parties'' shall follow the conditions, procedures, and provisions as follows.
 
−
 
 
−
 
 
−
==1. Term and Termination==
 
−
 
 
−
1.1. This ''Agreement'' takes effect on the ''Effective Date'', and remains in full force and effect for one year (hereinafter, the ''Term''). If no one ''Party'' expresses its willingness to end this ''Agreement'' 30 days before the ''Agreement'' ends, the ''Agreement'' prolongs for one more ''Term'' without any limit on the number of the ''Terms'' unless earlier terminated under this section, "[[#1. Term and Termination|1. Term and Termination]]".
 
−
 
 
−
1.2. Either ''Party'' may terminate this ''Agreement'' for any reason or no reason at all by providing the other ''Party'' written notice 14 calendar days in advance.
 
−
 
 
−
==2. Contractor Services==
 
−
 
 
−
2.1. During the ''Term'', the ''Company'' may engage the ''Contractor'' to provide the ''Company'' with the ''Services''.
 
−
 
 
−
2.2. The ''Contractor'' shall provide the necessary equipment to perform the ''Services''; the ''Company'' cannot be responsible for that equipment. If the ''Contractor'' has obtained employees or agents (hereinafter, the ''Contractor Personnel''), the ''Contractor''  shall be solely responsible for all costs associated with the ''Contractor Personnel''.
 
−
 
 
−
2.3. As a result of providing the ''Services'', the ''Contractor'' or ''Contractor Personnel'' may create certain one or more work products (hereinafter, the ''Work Product''). Regardless of other ''Work Products'', if any, are, the ''Services'' shall produce documentation including, but not limited to, description of the work done, [[source code]]s, etc.
 
−
 
 
−
2.4. The ''Contractor'' shall notify the ''Company'' of any change(s) to the ''Contractor's'' schedule that could adversely affect the availability of the ''Contractor'', whether known or unknown at the time of this ''Agreement'', no later than 30 days prior to such change(s). If the ''Contractor''  becomes aware of such change(s) within the 30 days period, the ''Contractor'' shall promptly notify the ''Company'' of such change(s) within a reasonable amount of time.
 
−
 
 
−
2.5. The ''Contractor'' shall issue invoices to the ''Company's'' accounts payable department within 30 days of completing the ''Services'', unless otherwise instructed by the ''Company'', and provide documentation as instructed by the ''Company's'' accounts payable department.
 
−
 
 
−
2.6. The ''Company'' shall pay to the ''Contractor'' within 30 days of receiving the invoice from the ''Contractor''. The ''Company'' offers methods of the payments; they are listed in Appendix B to this agreement. The ''Contractor'' shall specify the method of the ''Company's'' payments. If the ''Contractor'' specifies the way, which is not listed in Appendix B as a default, and some expenses and third-party fees are associated with that payment way, the ''Contractor'' is responsible for those expenses and fees.
 
−
 
 
−
2.7. Neither the ''Services'' nor ''Work Product'' shall include, rely on, and/or imply any proprietary licenses or commercial restrictions. If some software is needed to support the ''Services'' or be a part of the ''Work Product'', this software must be [[open-source]] only. If the intellectual property of that software is not in the public domain, the ''Contractor'' needs to seek the ''Company's'' approval on its use prior to the use.
 
−
 
 
−
2.8. Neither the ''Services'' nor ''Work Product'' shall include, rely on, and/or imply any external resources such as libraries, fonts, icons, images, or other files outside of the ''Work Product''. The ''Work Product'' shall be fully functional while being operated offline.
 
−
 
 
−
==3. Orders==
 
−
 
 
−
3.1. To engage the ''Contractor'', the ''Company'' uses official work requests (hereinafter, the ''Orders''). The ''Contractor'' may accept, decline, or request to clarify the ''Orders''
 
−
 
 
−
3.2. Any of the ''Orders'' shall contain one or more subject matters (hereinafter, the ''Subject Matter'') that the ''Company'' requests the ''Contractor'' to render. The ''Subject Matter'' can be either (a) a [[statement of work]] or another description of services or (b) request for time availability.
 
−
 
 
−
3.3. In order to be the ''Order'', in addition to other requirements stated in Section [[#9. Communications|9. Communications]] of the ''Agreement'', any of the ''Order'' shall have the word, "Order" or "Orders", in the title.
 
−
 
 
−
3.4. The ''Orders'' may or may not indicate special work compensation proposal, normally, money that the ''Company'' agrees to pay for the ''Services'' that the ''Company'' requests the ''Contractor'' to perform. The compensation model may be based on (a) specified rate, for instance, per hour of consultation, per translated word, or per processed image; in the case of specified rate, the ''Contractor's'' compensation depends on the amount of services rendered; (b) fixed-price project to produce the specified deliverable or deliverables; in the case of fixed-price project, the ''Contractor's'' compensation depends on the acceptance of the deliverables or another specified success of the project; or (c) combination of both, for instance, guaranteed specified rate and bonus in the case of project success.
 
−
 
 
−
3.5. Unless the ''Company'' specifies the compensation in the ''Orders'', the work performed by the ''Contractor'' shall be compensated at the rate, stated in Appendix A to this ''Agreement''. In that case, the ''Order'' shall state the number of paid hours that the ''Company'' authorizes the ''Contractor'' to work. The ''Order'' that specifies neither the compensation nor the number of authorized hours is invalid.
 
−
 
 
−
3.6. The ''Orders'' shall be treated as Appendixes to this ''Agreement''. To file them, they shall be indexed using the "S-[four-digit-year]-[two-digit-month]-[two-digit-day]" format. If more than one ''Order'' is sent in one day, the index shall also include the ordinal number; for example, "S-2023-07-12-2". No ambiguity in indexing may serve as an excuse for dismissal of any of the ''Orders''.
 
−
 
 
−
==4. Independent Contractor Status==
 
−
 
 
−
4.1. The ''Parties'' intend that the ''Contractor'' and any ''Contractor Personnel'' be engaged as independent contractors of the ''Company''. Nothing contained in this ''Agreement'' will be construed to create the relationship of employer and employee, principal and agent, partnership or joint venture, or any other fiduciary relationship.
 
−
 
 
−
4.2. The ''Contractor'' may not act as agent for, or on behalf of, the ''Company'', or to represent the ''Company'', or bind the ''Company'' in any manner.
 
−
 
 
−
4.3. The ''Contractor'' will not be entitled to worker's compensation, retirement, insurance or other benefits afforded to employees of the ''Company''.
 
−
 
 
−
4.4. The ''Company'' shall not be responsible for federal, state and local taxes derived from the ''Contractor's'' net income or for the withholding and/or payment of any federal, state and local income and other payroll taxes, workers' compensation, disability benefits or other legal requirements applicable to the ''Contractor''.
 
−
 
 
−
==5. Ownership==
 
−
 
 
−
5.1. The ''Contractor'' transfers and assigns to the ''Company'' all rights, titles and interests throughout the world in and to any and all ''Work Product''. This transfer and assignment includes, but is not limited to, the right to publish, distribute, make derivative works of, edit, alter or otherwise use the ''Work Product'' in any way the ''Company'' sees fit.
 
−
 
 
−
5.2. The ''Contractor'' cannot include any personal and/or contact information other than the ''Company's'' and/or authorized by the ''Company'' in any part of the ''Work Product'' and/or dispose while rending the ''Services''.
 
−
 
 
−
5.3. The ''Company'' grants the ''Contractor'', a limited, non-exclusive, non-transferable, non-assignable, royalty free, worldwide license to display the ''Work Product'' on a platform personally controlled, in whole or in part, by the ''Contractor''. The ''Contractor'' shall notify the ''Company'' about the display or displays. The ''Company'' may revoke this license at any time by requesting some alternation or the removal of the ''Work Product'' displayed by the ''Contractor''. Upon such request, the ''Contractor'' shall alternate or remove the ''Work Product'' from the platform, and provide written notification of such alternation or removal.
 
−
 
 
−
5.4. The ''Contractor'' grants the ''Company'', a limited, non-exclusive, non-transferable, non-assignable, royalty free, worldwide license to display the ''Contrator''<nowiki>'</nowiki>s information on a platform personally controlled, in whole or in part, by the ''Company''. The ''Company'' shall notify the ''Contractor'' about the display or displays. The ''Contractor'' may revoke this license at any time by requesting some alternation or the removal of the ''Contrator''<nowiki>'</nowiki>s information displayed by the ''Company''. Upon such request, the ''Company'' shall alternate or remove the ''Contrator''<nowiki>'</nowiki>s information from the platform, and provide written notification of such alternation or removal.
 
−
 
 
−
==6. Representations==
 
−
 
 
−
Both ''Parties'' represent that they are fully authorized and empowered to enter into this ''Agreement'', and that the performance of the obligations under this ''Agreement'' will not violate or infringe upon the rights of any third-party, or violate any agreement between the Parties and any other person, firm or organization or any law or governmental regulation.
 
−
 
 
−
==7. Indemnification==
 
−
 
 
−
The ''Contractor'' shall defend, indemnify, and hold harmless the ''Company'', its affiliates, and its respective officers, directors, agents and employees from any and all claims, demands, losses, causes of action, damage, lawsuits, judgments, including attorneys' fees and costs, arising out of, or relating to, the ''Contractor's'' representation and services under this ''Agreement''.
 
−
 
 
−
==8. Confidential Information==
 
−
 
 
−
8.1. Each ''Party'' (on its behalf and on behalf of its subcontractors, employees or representatives, or agents of any kind) agrees to hold and treat all confidential information of the other ''Party'', including, but not limited to, trade secrets, sales figures, employee and customer information and any other information that the receiving ''Party'' reasonably should know is confidential (hereinafter, the ''Confidential Information'') as confidential and protect the ''Confidential Information'' with the same degree of care as each ''Party'' uses to protect its own ''Confidential Information'' of like nature.
 
−
 
 
−
8.2. The ''Confidential Information'' does not include any information that (i) at the time of the disclosure or thereafter is lawfully obtained from publicly available sources generally known by the public (other than as a result of a disclosure by the receiving ''Party'' or its representatives); (ii) is available to the receiving ''Party'' on a non-confidential basis from a source that is not and was not bound by a confidentiality agreement with respect to the ''Confidential Information''; or (iii) has been independently acquired or developed by the receiving ''Party'' without violating its obligations under this ''Agreement'' or under any federal or state law.
 
−
 
 
−
8.3. The ''Contractor Personnel'' shall not access any ''Confidential Information'' without a separate [[non-disclosure agreement]] between the ''Company'' and an individual who is a part of the ''Contractor Personnel'' and who needs that access.
 
−
 
 
−
==9. Communications==
 
−
 
 
−
9.1. All the communications between the ''Parties'' that are related to this ''Agreement'' most likely occur electronically.
 
−
 
 
−
9.2. Email communication is the only official. The ''Parties<nowiki>'</nowiki>'' email addresses are stated in Appendix C to this ''Agreement''. To be relevant to this ''Agreement'', the emails must have words "Bskol", "Careerprise", and/or "iDosvid" and "Contract" in their titles. Then, they can be presented during possible litigation.
 
−
 
 
−
9.3. Unless another arrangement is negotiated, the ''Contractor'' shall provide the ''Company'' with weekly reports on (i) what work has been done within the last week, (ii) what work is going to be done within the current week, and (iii) what problems, if any, the ''Contractor'' seeks to be solved on the ''Company's'' side.
 
−
 
 
−
9.4. Unofficial communications such as discussions and negotiations may occur via recorded or unrecorded conferences, publications, etc.
 
−
 
 
−
9.5. The ''Parties'' plea to try, sincerely and in a good faith, to resolve any disputes that may occur between the ''Parties'' before any possible litigation.
 
−
 
 
−
==10. Limited Warranty==
 
−
 
 
−
10.1. The ''Contractor'' does not provide any warranty that operation of any services hereunder will be uninterrupted or error-free.
 
−
 
 
−
10.2. The ''Contractor'' warrants that all services are be performed in a professional manner in accordance with generally applicable industry standards and laws. That provision includes, but not limited to, the respect to third-party intellectual properties, open-source software licenses, etc.
 
−
 
 
−
10.3. Between the ''Parties'', the ''Contractor's'' sole liability (and the ''Company's'' exclusive remedy) for any breach of this warranty shall be for the ''Contractor'' to re-perform any deficient services, or, if the ''Contractor'' is unable to remedy such deficiency within thirty (30) days, to void the invoice for the deficient services. The ''Contractor'' shall have no obligation with respect to a warranty claim if the claim is the result of third-party hardware or software malfunctioning, the actions of the ''Company'' or some other party or is otherwise caused by factors outside the reasonable control of the ''Contractor''.
 
−
 
 
−
10.4. This section, "[[#10. Limited Warranty|10. Limited Warranty]]", is a limited warranty, and sets forth the only warranties made by any ''Party''. Any ''Party'' makes no other warranties, conditions, or undertakings, express or implied, statutory or otherwise, including but not limited to warranties or merchantability, fitness for a particular purpose or non-infringement or any warranties regarding the performance of anything provided or installed by the ''Contractor''.
 
−
 
 
−
==11. Miscellaneous Provisions==
 
−
 
 
−
11.1. This ''Agreement'', and any accompanying appendices, duplicates, or copies, constitutes the entire agreement between the ''Parties'' with respect to the subject matter of this ''Agreement'', and supersedes all prior negotiations, agreements, representations, and understandings of any kind, whether written or oral, between the ''Parties'', preceding the date of this ''Agreement''.
 
−
 
 
−
11.2. This ''Agreement'' may be amended only by written agreement duly executed by an authorized representative of each ''Party''. To alternate any Appendix unilaterally, one ''Party'' shall notify another ''Party'' no fewer than 30 days before the change. The alternation of Appendices may not effect the work conditions for those ''Orders'' that have already been accepted.
 
−
 
 
−
11.3. If any provision or provisions of this ''Agreement'' shall be held unenforceable for any reason, then such provision shall be modified to reflect the ''Parties<nowiki>'</nowiki>'' intention. All remaining provisions of this ''Agreement'' shall remain in full force and effect for the duration of this ''Agreement''.
 
−
 
 
−
11.4. This ''Agreement'' shall not be assigned by either party without the express consent of the other party.
 
−
 
 
−
11.5. A failure or delay in exercising any right, power or privilege in respect of this ''Agreement'' will not be presumed to operate as a waiver, and a single or partial exercise of any right, power or privilege will not be presumed to preclude any subsequent or further exercise, of that right, power or privilege or the exercise of any other right, power or privilege.
 
−
 
 
−
11.6. This ''Agreement'' is be governed by and construed in accordance with the laws of the State of ­­­­­­­­­­­­Virginia without reference to any principles of conflicts of laws, which might cause the application of the laws of another state. Any action instituted by either party arising out of this ''Agreement'' will only be brought, tried and resolved in the applicable federal or state courts having jurisdiction in the Commonwealth of Virginia. Each ''Party'' hereby consents to the exclusive personal jurisdiction and venue of the courts, state and federal, having jurisdiction in the Commonwealth of Virginia.
 
−
 
 
−
The ''Parties'' are signing this ''Agreement'' electronically on the dates stated below.
 
−
 
 
−
[[Virginia Institute of Technology]]
 
−
 
 
−
*By: ____________________ ''[Signature]''
 
−
*Name, title: Gary Ihar, director
 
−
*Date: ____________________ ''[Month, Day]'', 2023
 
  
−
____________________ ____________________ [CONTRACTOR NAME]
+
===Turn around time===
 +
:When following the steps to claim a transcription task from the transcripts list, contractors should set the due date in Step 4 to reflect completion of the transcript within a maximum of two days or less from the date the transcription task was claimed. After accessing the transcripts list in Step 1, locating the desired task in Step 2, entering your name in the "Contractor" column in Step 3, and indicating the due date in Step 4, the claimed transcript development should then be finished within the due date indicated of less than two days or unless additional time was approved during claiming due to unusual circumstances.
  
−
*By: ____________________ ''[Signature]''
+
==Contracting==
−
*Name, title: ____________________ ____________________ ''[Contractor's name and, if the Contractor represents an organization, title]''
 
−
*Date: ____________________ ''[Month, Day]'', 2023
 
  
−
==Appendices==
+
===Order===
−
===Appendix A===
+
: (For [[Careerprise contractor agreement]])
−
:Unless the ''Orders'' specify another rate, the default rate for the ''Services'' is ____________________ ''[Number]'' US dollars per ten minutes of audio transcription.
+
:# The ''Contractor'' shall provide the ''Company'' with transcription services according to the requirements stated on the https://wiki.cnmcyber.com/en/CNMCyber_transcript page.
 +
:# The ''Company'' shall compensate the ''Contractor'' at the rate of $ ___ per minute of the transcripted audio.
  
−
===Appendix B===
+
===Transcription Tasks===
−
:The ''Contractor'' uses ____________________ (''by default, [[Payoneer]] or [[PayPal]]'') to bill the ''Company''.
 
  
−
===Appendix C===
+
{| class="wikitable"
−
:For the purposes of this ''Agreement'', the ''Company's'' email is ____________________ ____________________ ; the ''Contractor's'' email is ____________________ ____________________ .
+
|-
 +
! Title !! Event Date !! Video Link !! Duration !! Transcript Page !! Contractor !! Due Date !! Complete
 +
|-
 +
| Careerprise pitch || 04/09/23 || https://youtu.be/p3PSZLEoRuo || 29:35 || [[Talk:Careerprise pitch]] || Anthony || 08/09/23 ||  Yes
 +
|-
 +
|-
 +
| Event transcription requirements || 02/08/23 || https://www.youtube.com/watch?v=pa5zQx5vU6o || 26:03 || [[Talk:CNMCyber event]] ||  || ||  Yes
 +
|-
 +
| CNMCyber Office Hours requirements (part 2) || 20/07/23 || https://youtu.be/VBp6iJ-YihM || 25:46 || [[Talk:CNMCyber Office Hours]] ||  || ||  Yes
 +
|-
 +
| CNMCyber Office Hours requirements (part 1) || 15/07/23 || https://youtu.be/zcc4f_4qg5A || 25:46 || [[Talk:CNMCyber Office Hours]] ||  || || Yes
 +
|-
 +
| CNMCyber event requirements || 10/07/23 || https://youtu.be/VgYursiLRoI || 21:48 || [[Talk:CNMCyber event]] ||  || || Yes
 +
|-
 +
| CNMCyber Development: From hours to contracts || 06/07/23 || https://youtu.be/8KX9Elw-O-0 || 33:12 || [[Talk: From hours to contracts]] || Anthony || 15/09/23 || Yes
 +
|-
 +
| CNM Social user-group requirements || 05/07/23 || https://youtu.be/tAFZzBX89R4 || 46:35 || [[Talk:CNM Social]] || Anthony || 21/09/23 || Yes
 +
|-
 +
| Tech-Board requirements (Part 2) || 05/07/23 || https://youtu.be/Z4eFfsM9IlM || 41:59 || [[Talk:CNM Technology Board]] || Anthony || 17/09/23  || Yes
 +
|-
 +
| Website purposes for IA || 29/06/23 || https://youtu.be/7z56_IhZEPk || 38:51 || [[Talk:Website IA]] || Anthony || 03/10/23 || Yes
 +
|-
 +
| CNM Tube requirements || 28/06/23 || https://youtu.be/QFhgg8uc1e0 || 54:34 || [[Talk:CNM Tube]] || Anthony || 10/10/23 || Yes
 +
|-
 +
| This-Week series requirements || 26/06/23 || https://youtu.be/ZtiJ9Ql0-ZI || 33:01 || [[Talk:CNMCyber This Week]] || Anthony || 08/10/23 || Yes
 +
|-
 +
| Website IA sprint || 24/06/23 || https://youtu.be/-l7gJNlinso || 32:07 || [[Talk:CNMCyber.com IA]] || Anthony || 06/10/23 || Yes
 +
|-
 +
| Personas for Friends Of CNM website || 21/06/23 || https://youtu.be/aNSHyvt07U8 || 39:34 || [[Talk:FriendsOfCNM.com IA]] || Anthony || 08/10/23 || Yes
 +
|-
 +
| CNMCyber.com IA and IA generally || 15/06/23 || https://youtu.be/7fXkON5rtVw || 27:17 || [[Talk:CNMCyber.com IA]] || Anthony  || 01/10/23 || Yes
 +
|-
 +
| Tech-Board requirements (Part 1) || 13/06/23 || https://youtu.be/p3GrmsDVbnI || 11:19 || [[Talk:CNM Technology Board]] || Anthony || 16/09/23 || Yes
 +
|-
 +
| Website IA initiation || 08/06/23 || https://youtu.be/inzTVq140mg || 38:29 || [[Talk:Website IA]] || Anthony || 04/10/23 || Yes
 +
|}

Latest revision as of 17:35, 11 October 2023

CNMCyber transcript is technically wording which is used in CNMCyber Office Hours events. In the best case scenario, it should be typed and moved to the requirements.

The transcript can also be defined as the record of someone's requirement.

The transcript is also an intermediate product, it's not a final product. It's a deliverable but is not user deliverable. It's a sub-product. So then when the transcript is available, a wikipage can be developed from the requirements in the transcript.


Transcript Development for CNMCyber Events

Purpose and Importance of Transcription

  • To have a written record of requirements discussed during the event.
  • Support traceability between event discussions and final wiki pages. The transcript itself leads to requirements. The transcript isn't the final product, but the requirements that a customer agrees to become the actual product. This can be measured, and in the best situation, it should be a requirements traceability matrix (RTM) record.
For example, when you write down requirements on a page, imagine it's what you're presenting to your boss or customer. You're saying, "This is what you'll get." You list down everything – like having HumHub, Odoo, Jitsi set up in a certain way, using ProxmoxVE, making it highly available with three nodes, having a public IPv4 network, running on Apache and Nginx, using Ceph for storage, and routing with pfSense. You ask, "Is this what you want?" They either sign or confirm via email. This becomes a kind of blueprint.

Components of a transcript

A transcript should focus on important information, omitting irrelevant details. A transcript should omit things like;
  • "my name is _ _ _"
  • "sorry I need to drink my coffee,"
  • "give me a post I will like,"
  • "I will answer another call."
It's not important. So a transcript should include what is important, what should be and what can be moved to requirements.

Transcription for CNMCyber Events

Transcripts will be developed on wiki project page (currently - discussion page) of the product page. The main page is the product and discussion will be a project. Project (current discussion page), here there will be information how the product was developed and what requirements were involved.

Target Audience and Deliverables

A developer working on the product is the target audience of the transcript. Transcript by itself is the intermediate product, the product page is the end product and transcript is a part of development with a deliverable.

Success Criteria and Desired Outcome

Success for a transcript is determined by how useful it is. The goal is having Wiki Pages that describe products. For example; we need to have this platform on which our Jitsi will work, which is called talk and we will do this conference one day on the Talk.cnmcyber.com slash something - So right now we are doing this on employableU which is temporary. So the end product is the service but to build this firm we need to have a description of what we are doing, what we need to look for, and what we need to do. So now, in this case the desired out come is a working technology.
The technical sense, quality is confirmation the description of the product matches the product itself right. So we have requirements and we have a product. If there's gaps, it's a quality product. But to know that you have a quality product you need to have a description, if you don't have a description how would you know? Transcription is a good way to build this description.

How to claim a transcription task

If you are a contractor developing transcripts for CNMCyber Office Hours you will need to;
  1. Go to Talk:CNMCyber transcript to access the transcription tasks list
  2. Find the title of the task you would like to create a transcript for
  3. In the "Contractor" column on the row for that task, write your name to indicate you will be responsible for this transcript
  4. In the "Due Date" column on the same row, enter the date when you expect the transcript to be completed
  5. Notify your CNMCyber contact when you have claimed a task so they know it is assigned
  6. Develop the transcript according to the description requirements best described on this wiki page
  7. Once complete, notify your CNMCyber contact person.
  8. If you have any questions about the task, get clarification from your CNMCyber contact before claiming and beginning work.

Steps to create a transcript

  1. Transcribe the audio - This can be done manually by listening and typing or if the event is posted on YouTube Channel you can extract the transcript by clicking on the three dots at the bottom right of the video and select show transcript. A side bar will be displayed with the transcript and time stamps. Highlight the entire transcript then copy and paste to the page where you will create the transcript from.
  2. Clean up the transcript - correct any mistakes in the transcription, eliminate timestamps, and filler words such as "um," "hmm," "oh," "like," "you know," "so", as well as any unnecessary side conversations or interruptions that shouldn't be in the final transcript. Also remove any repetitions.
  3. Structure the information - Break the transcript into logical sections using headers. For example, you may have a section for Introduction, topics that were discussed in the meeting
  4. Focus on key points - Summarize the transcript while paying attention to key questions, decisions, and discussion points that are relevant for the requirements of the product.
  5. Review the scrip - Go over the draft transcript and make any final edits to improve clarity. The goal is to create a traceable record of the event that can used to create product requirements.
  6. Stick to the requirements - Make sure the transcript contains the information needed for the product requirements.
  7. Add attributions - Note who said what using speaker attributions like "Kevin:".
  8. Add attribute questions - Note who asked each question using "[Name] asked:".
  9. Add attribute answers - Indicate who provided each answer using "[Name] answered:".
  10. Check accuracy - Verify names, titles, terminology, and facts.
  11. Save the transcript - Save the transcript to the discussion page (project page) of the product being developed.
  12. Ask clarifying questions - Get any needed context before beginning to create the transcript.

Turn around time

When following the steps to claim a transcription task from the transcripts list, contractors should set the due date in Step 4 to reflect completion of the transcript within a maximum of two days or less from the date the transcription task was claimed. After accessing the transcripts list in Step 1, locating the desired task in Step 2, entering your name in the "Contractor" column in Step 3, and indicating the due date in Step 4, the claimed transcript development should then be finished within the due date indicated of less than two days or unless additional time was approved during claiming due to unusual circumstances.

Contracting

Order

(For Careerprise contractor agreement)
  1. The Contractor shall provide the Company with transcription services according to the requirements stated on the https://wiki.cnmcyber.com/en/CNMCyber_transcript page.
  2. The Company shall compensate the Contractor at the rate of $ ___ per minute of the transcripted audio.

Transcription Tasks

Title Event Date Video Link Duration Transcript Page Contractor Due Date Complete
Careerprise pitch 04/09/23 https://youtu.be/p3PSZLEoRuo 29:35 Talk:Careerprise pitch Anthony 08/09/23 Yes
Event transcription requirements 02/08/23 https://www.youtube.com/watch?v=pa5zQx5vU6o 26:03 Talk:CNMCyber event Yes
CNMCyber Office Hours requirements (part 2) 20/07/23 https://youtu.be/VBp6iJ-YihM 25:46 Talk:CNMCyber Office Hours Yes
CNMCyber Office Hours requirements (part 1) 15/07/23 https://youtu.be/zcc4f_4qg5A 25:46 Talk:CNMCyber Office Hours Yes
CNMCyber event requirements 10/07/23 https://youtu.be/VgYursiLRoI 21:48 Talk:CNMCyber event Yes
CNMCyber Development: From hours to contracts 06/07/23 https://youtu.be/8KX9Elw-O-0 33:12 Talk: From hours to contracts Anthony 15/09/23 Yes
CNM Social user-group requirements 05/07/23 https://youtu.be/tAFZzBX89R4 46:35 Talk:CNM Social Anthony 21/09/23 Yes
Tech-Board requirements (Part 2) 05/07/23 https://youtu.be/Z4eFfsM9IlM 41:59 Talk:CNM Technology Board Anthony 17/09/23 Yes
Website purposes for IA 29/06/23 https://youtu.be/7z56_IhZEPk 38:51 Talk:Website IA Anthony 03/10/23 Yes
CNM Tube requirements 28/06/23 https://youtu.be/QFhgg8uc1e0 54:34 Talk:CNM Tube Anthony 10/10/23 Yes
This-Week series requirements 26/06/23 https://youtu.be/ZtiJ9Ql0-ZI 33:01 Talk:CNMCyber This Week Anthony 08/10/23 Yes
Website IA sprint 24/06/23 https://youtu.be/-l7gJNlinso 32:07 Talk:CNMCyber.com IA Anthony 06/10/23 Yes
Personas for Friends Of CNM website 21/06/23 https://youtu.be/aNSHyvt07U8 39:34 Talk:FriendsOfCNM.com IA Anthony 08/10/23 Yes
CNMCyber.com IA and IA generally 15/06/23 https://youtu.be/7fXkON5rtVw 27:17 Talk:CNMCyber.com IA Anthony 01/10/23 Yes
Tech-Board requirements (Part 1) 13/06/23 https://youtu.be/p3GrmsDVbnI 11:19 Talk:CNM Technology Board Anthony 16/09/23 Yes
Website IA initiation 08/06/23 https://youtu.be/inzTVq140mg 38:29 Talk:Website IA Anthony 04/10/23 Yes
Retrieved from "https://wiki.cnmcyber.com/w/index.php?title=CNMCyber_transcript&oldid=118009"