Page tree
Skip to end of metadata
Go to start of metadata

Note: If you are adding abbreviations to this Glossary

  • put the full text in the Term's "Title" field,
  • the actual abbreviation in "Abbreviation(s)" field. 
  • put a more detailed description in the "Definition" field.

We are don't yet have a policy for the Label field, but possibilities are:

  • Indicating the provenance (For example DBD_Acronym indicates the term is from the DBD list of acronyms).
  • Indicating the domain of relevance in order to resolve ambiguities (Maybe this could resolve to a sub-system or professional field).

This needs some curation mechanism as well.


  • Analogue-to-Digital Unit (used only for SKA1-Low)

    Jan 21, 2022 (04:46)
  • Analogue-Digital Converter

    Jan 21, 2022 (04:46)
  • ...
53 Terms
A
  • Build-out and Evolution extensions

    Jan 21, 2022 (04:46)
  • Building Management System

    Jan 21, 2022 (04:46)
  • ...
16 Terms
B
  • Citizen Band

    Jan 21, 2022 (04:46)
  • Change Review Board

    Jan 21, 2022 (04:46)
  • ...
74 Terms
C
  • Digital Step Attenuator

    Jan 21, 2022 (04:46)
  • Digital Signal Processing

    Jan 21, 2022 (04:46)
  • ...
51 Terms
D
  • enhanced Telecommunications Operations Model

    Jan 21, 2022 (04:46)
  • enhanced Telecommunications Applications Model

    Jan 21, 2022 (04:46)
  • ...
43 Terms
E
  • Factory Acceptance Test

    Jan 21, 2022 (04:46)
  • Failure

    Jan 21, 2022 (04:46)
  • ...
43 Terms
F
  • Ground Plane

    Jan 21, 2022 (04:46)
  • Green Bank Telescope

    Jan 21, 2022 (04:46)
  • ...
15 Terms
G
  • Housed

    Jan 21, 2022 (04:46)
  • Historical Data Base

    Jan 21, 2022 (04:46)
  • ...
18 Terms
H
  • Integrated Task Team

    Jan 21, 2022 (04:46)
  • Integrated Pulse Profile

    Jan 21, 2022 (04:46)
  • ...
57 Terms
I
  • Jansky Very Large Array (aka EVLA)

    Jan 21, 2022 (04:46)
  • JavaScript Object Notation

    Jan 21, 2022 (04:46)
  • ...
5 Terms
J
  • Karoo Radio Astronomy Observatory

    Jan 21, 2022 (04:46)
  • Karoo Array Telescope - SKA Precursor in South Africa

    Jan 21, 2022 (04:46)
  • ...
9 Terms
K
  • Local Sky Model

    Jan 21, 2022 (04:46)
  • Local Sidereal Time

    Jan 21, 2022 (04:46)
  • ...
24 Terms
L
  • Model Image

    Jan 21, 2022 (04:46)
  • Model

    Jan 21, 2022 (04:46)
  • ...
35 Terms
M
  • New Engineering Contract version 4

    Jan 21, 2022 (04:46)
  • New Engineering Contract version 3

    Jan 21, 2022 (04:46)
  • ...
16 Terms
N
  • open-source

    Jan 21, 2022 (04:46)
  • Open Platform Communications Unified Architecture

    Jan 21, 2022 (04:46)
  • ...
35 Terms
O
  • Portability

    Jan 21, 2022 (04:46)
  • Polyphase Filter Bank

    Jan 21, 2022 (04:46)
  • ...
71 Terms
P
  • Quality Assessment

    Jan 21, 2022 (04:46)
  • Qualificaton Test Results

    Jan 21, 2022 (04:46)
  • ...
5 Terms
Q
  • Roll-out

    Jan 21, 2022 (04:46)
  • Ring Main Unit

    Jan 21, 2022 (04:46)
  • ...
33 Terms
R
  • Stokes Parameters

    Jan 21, 2022 (04:46)
  • Station Timing and Frequency Reference

    Jan 21, 2022 (04:46)
  • ...
135 Terms
S
  • Tele-Management Forum

    Jan 21, 2022 (04:46)
  • Technology Roadmap

    Jan 21, 2022 (04:46)
  • ...
51 Terms
T
  • Use Case

    Jan 21, 2022 (04:46)
  • Unmanned Aerial Vehicle

    Jan 21, 2022 (04:46)
  • ...
11 Terms
U
  • Very Coarse Channelizer

    Jan 21, 2022 (04:46)
  • Verification System

    Jan 21, 2022 (04:46)
  • ...
20 Terms
V
  • Workmanship

    Jan 21, 2022 (04:46)
  • Work Breakdown Structure element or Work Element

    Jan 21, 2022 (04:46)
  • ...
19 Terms
W
0 Term
X
  • Yuan Renminbi

    Jan 21, 2022 (04:46)
  • ...
1 Term
Y
Z

14 Comments

  1. I was wondering where to put notes on the Glossary trial, and I decided this was the best place. My thoughts are:

    • We clearly need a process/workflow for curating these definitions.
    • I can't work out (and find it irritating) how to edit the term name. The only way I can do it is delete and re-create the term.
    • I would like to be able to extract a CSV or Excel sheet containing the terms using an API.
    1. I agree that it would be very valuable and that we need a curated worklflow. It will be quite a of work to align terms though... We have been terrible in this up to now, especially with the numerous Consortia and Partners all having their own definitions.

      With Product/item names, we should try to stick to the PBS in eB (or fix it). I suppose the first documents we should try to align are our top-level documents like the L1 Requirements and DBD?

  2. I somehow managed to create the following definition, but I am sure I didn't do it consciously, but I suspect I did it while editing the note at the top of this page. It could be a weird bug.

  3. The glossary works site wide, and highlights terms without regard for context. May be a curation issue, but Confluence explaining to me that a CPU core is "An area 1000 m in diameter within which the individual stations are randomly located with no overlap" is at best amusing.


    1. Hi Chris, yes this is an issue, but I don't see it as a major problem - better for people to understand that a term they use has other definitions, than to be ignorant of it. I think if we go ahead with this, then labels may become important (or else multiple different glossaries).

      1. This also means that we can flag up conflicting acronyms used across the organisation, and arrange to spell them out whenever it's an issue.

        (Thus in SDP I insisted we only used IP to stand for Internet Protocol (and then only if used in e.g. the TCP/IP context). Otherwise, we had to spell out whether we meant Internet Protocol or Intellectual Property. )

        It may also help curtail the uncontrollable spread of acronyms.


        1. Fair enough, sounds reasonable.


        2. As a note on abreviations, the glossary is able to display more than 1 term with a shared abbreviation. They can be cycled through using the little dots in the top right hand corner. As Nick Mentioned this is where lables will become much more useful in future to give context.

          1. Yes, I can think that this would be valuable. IP, for example, is also a globally accept abbreviation for Intellectual Property. So we really will need to allow this.

  4. Hmm. The definition for Ionosphere has been given a synonym of 'I'. You can see from this how this could be annoying :

    1. Yes. This has been pointed out a number of times. It isn't a good abbreviation. Blame Dewdney, Peter

  5. Please can we add currency codes used by our members thus:

    Australian Dollar AUD

    Canadian Dollar CAD

    Yuan Renminbi CNY

    Euro EUR

    Indian Rupee INR

    New Zealand Dollar NZD

    Rand ZAR

    Swedish Krona SEK

    Swiss Franc CHF

    Pound Sterling GBP

    from https://www.iso.org/iso-4217-currency-codes.html

    1. these have now been added

      1. Wow, thanks for the fast work Rob, much appreciated!