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.


  • AA0.5
    Jul 8, 2021 (18:12)
  • Academic and Research Network
    Aug 6, 2020 (17:10)
  • ...
52 Terms
A
  • Building Management System
    Aug 6, 2020 (17:10)
  • Building Automation and Control network
    Aug 6, 2020 (17:10)
  • ...
16 Terms
B
  • Co-Investigator
    Aug 6, 2020 (17:10)
  • Coarse Wavelength-Division Multiplexing
    Aug 6, 2020 (17:10)
  • ...
72 Terms
C
  • Dish Fibre Network
    May 24, 2021 (11:25)
  • Dish Element/Consortium
    Aug 6, 2020 (17:11)
  • ...
50 Terms
D
  • Engineering Network
    Aug 5, 2020 (11:24)
  • Engineering Management System
    Aug 6, 2020 (17:11)
  • ...
43 Terms
E
  • Frequency Slice
    Aug 6, 2020 (17:11)
  • Frequency accuracy
    Aug 5, 2020 (11:24)
  • ...
42 Terms
F
  • Global Positioning System
    Aug 5, 2020 (12:02)
  • Global Navigation Satellite System
    Aug 6, 2020 (17:11)
  • ...
15 Terms
G
  • Historical Data Base
    Aug 6, 2020 (17:11)
  • High voltage
    Aug 6, 2020 (17:11)
  • ...
16 Terms
H
  • Ionosphere
    Aug 6, 2020 (17:11)
  • Inverse Polyphase Filterbank
    Sep 3, 2020 (09:53)
  • ...
55 Terms
I
  • Jansky Very Large Array (aka EVLA)
    Aug 6, 2020 (17:11)
  • JavaScript Object Notation
    Aug 6, 2020 (17:11)
  • ...
4 Terms
J
  • Key Science Project
    Aug 6, 2020 (17:11)
  • Key Performance Indicator
    Jan 14, 2021 (09:08)
  • ...
9 Terms
K
  • Local Monitor and Control
    Aug 6, 2020 (17:11)
  • Local Area Network
    Aug 6, 2020 (17:11)
  • ...
23 Terms
L
  • Mid-Frequency Aperture Array
    Aug 6, 2020 (17:11)
  • Middleware
    Aug 5, 2020 (11:24)
  • ...
31 Terms
M
  • Network Equipment Building System
    Aug 6, 2020 (17:11)
  • National Research Foundation (South Africa)
    Aug 6, 2020 (17:11)
  • ...
16 Terms
N
  • Organisational Level maintenance
    Aug 5, 2020 (11:24)
  • Optimised Candidate List and Data
    Aug 6, 2020 (17:11)
  • ...
35 Terms
O
  • Pact
    Sep 4, 2020 (09:25)
  • P4
    Jun 1, 2021 (17:56)
  • ...
66 Terms
P
  • Qualificaton Test Procedure
    Aug 6, 2020 (17:11)
  • Quad Ridge Feed Horn
    Aug 6, 2020 (17:11)
  • ...
5 Terms
Q
  • Restored Image
    Aug 5, 2020 (11:24)
  • Residual Image
    Aug 5, 2020 (11:24)
  • ...
31 Terms
R
  • Signal and Data Transport Element/Consortium
    Aug 6, 2020 (17:11)
  • Signal and Data Transport
    Feb 5, 2021 (13:39)
  • ...
131 Terms
S
  • Telescope Issue Management System New
    Aug 6, 2020 (17:12)
  • Telescope Issue Management System
    Aug 6, 2020 (11:24)
  • ...
51 Terms
T
  • United Nations Educational, Scientific and Cultural Organization
    Aug 6, 2020 (17:12)
  • United Kingdom
    Aug 6, 2020 (17:12)
  • ...
10 Terms
U
  • VLBI Data Interchange Format
    Aug 6, 2020 (17:12)
  • Visual Monitoring System
    Aug 6, 2020 (17:12)
  • ...
20 Terms
V
  • Well-formed requirement
    Aug 5, 2020 (11:25)
  • Weighting
    Aug 5, 2020 (11:25)
  • ...
18 Terms
W
0 Term
X
  • Yuan Renminbi
    Nov 12, 2020 (18:55)
  • ...
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!