WIP - Batch & Dynamic Scoring

Esse_Chua
Esse_Chua Posts: 23 QUANTEXA TEAM
in Quantexa Community Library

Please respond to the below questions:

  1. Has this content piece had a technical review by a TL (from a content accuracy and editorial perspective) Technical / Product content only
    • The editorial review must follow guidance from the Docs team, please use the resources linked at the bottom.
  2. If part of the Tech Lead team - please use the tag 'Tech-Lead-Content'
  3. Who is your piece aimed at? (Data Engineer, Data Scientist, Investigator, Delivery Manager, etc.)
  4. Can the article be linked to another piece/area of the Community?:
    1. A Specialist User Group (Data Management, FinCrime, KYC, or Insurance)
    2. Another related article in the Community
  5. What is the purpose of your piece? Please include a summary line at the top of the blog.
  6. Have you reviewed the content classification guidelines? Can the content be open to the public (i.e. searchable via Google) does it need to be restricted, or internal only?
    1. Please choose from the following:
      1. ✔️Public✔️- Content which is publicly viewable on the internet.
        1. Please note, the assumption is all content should be made public where possible due to the increased impact benefits
      2. 🔑Restricted🔑- Viewable by registered Customers and Partners, in addition to employees.
        1. For restricted content - Please provide a rationale for why this must be restricted.
        2. Create a short summary which can be posted in a public area of the Community - this short summary will link to the article and promote it.
      3. 🛑Internal🛑 - Viewable by Quantexa employees only.
  7. Is there an urgency to publishing or preferential timeframe?
  8. Please specify the most suitable section of the Community Library for publishing.
  9. Editorial checklist:
    1. Have you capitalized any Quantexa terms like 'Entity', 'Document' and 'Entity Resolution'? (check the docs site Glossary if you aren't sure)
    2. Have you included a short intro paragraph at the top of the article, outlining the purpose and target audience, and a concluding paragraph including any relevant links to associated content?
    3. Have you used American (US) English - for example, 'analyze' not 'analyse'?
    4. Have you used headings, bullet points and tables to break up the content and grey boxes for code snippets?
  10. Please include aliases, otherwise known as lines or alternate keywords for any terms you have used that are known by multiple names. This helps people find your piece even if they have not used the exact terms you've included. E.g. 'Elasticsearch (or Elastic)'
  11. If you need further editorial guidance (beyond the guides below), tag James Parry or Ffion Owen.

Editorial Resources

Become a better writer ↗

Content models ↗

Quantexa writing guide ↗

Editing tools: Grammarly and Hemingway

Topics