Help:Wiki-Dev

From GRS Documentation Wiki

TODOs

Data Structures

Guiding principals of Data Structures

Leave more administrative content to the department's sharepoint (rule of thumb: anything the secretaries might need to read/edit, should be on sharepoint). (TODO: add link to sharepoint)

A semantic wiki instance might look like it has sections, but in essence it is all based on different "categories" of pages. For the most part, it is a flat page hierarchy (NO Subpages).

[SMW Help:Classification](https://www.semantic-mediawiki.org/wiki/Help:Classification) provides good info on using Categories and Properties to classify wiki pages.

Categories[1]

Categories are the main way to define what kind of a thing a page refers to.


All Categories and their Parent Categories

 parent"Subcategory of" is a predefined property to define that a category is a subcategory of another and is provided by Semantic MediaWiki.
AGAGEMedusaDivAgilent5973GCDivMSgaschromatograph-online
AGAGEMedusaDivAgilent5973GCDivMS
AGAGEMedusaDivAgilent5973GCDivMS
AGAGEMedusaDivAgilent6890NDivAgilent5975BMSgaschromatograph-online
AGAGEMedusaDivAgilent6890NDivAgilent5975BMS
AGAGEMedusaDivAgilent6890NDivAgilent5975BMS
ANSTO1500Lradondetector
ANSTO1500L
ANSTO1500L
Aero-LaserAL5001vacuumultra-violetfluorescencedetector
Aero-LaserAL5001
Aero-LaserAL5001
Aero-LaserAL5002vacuumultra-violetfluorescencedetector
Aero-LaserAL5002
Aero-LaserAL5002
AerodyneCAPSNO2Monitorcavityattenuatedphaseshiftspectrometer
AerodyneCAPSNO2Monitor
AerodyneCAPSNO2Monitor
AerodyneCAPSNO2ambientcavityattenuatedphaseshiftspectrometer
AerodyneCAPSNO2ambient
AerodyneCAPSNO2ambient
AerodyneCI-API-TOFchemicalionization-atmosphericpressureinterface-timeofflightmassspectrometer
AerodyneCI-API-TOF
AerodyneCI-API-TOF
AerodyneCI-API-TOFiodideCIMSchemicalionization-atmosphericpressureinterface-timeofflightmassspectrometer
AerodyneCI-API-TOFiodideCIMS
AerodyneCI-API-TOFiodideCIMS
AerodyneCI-API-TOFnitrateCIMSchemicalionization-atmosphericpressureinterface-timeofflightmassspectrometer
AerodyneCI-API-TOFnitrateCIMS
AerodyneCI-API-TOFnitrateCIMS
AerodyneQ-ACSMparticlemassspectrometer-quadrupole
AerodyneQ-ACSM
AerodyneQ-ACSM
AerodyneToF-ACSMparticlemassspectrometer-time-of-flight
AerodyneToF-ACSM
AerodyneToF-ACSM
AerodyneToF-ACSM-Xparticlemassspectrometer-time-of-flight
AerodyneToF-ACSM-X
AerodyneToF-ACSM-X
AerodyneVOCUSprotontransfermassspectrometer
AerodyneVOCUS
AerodyneVOCUS
Aerodynecustombuiltthermaldissociationcavityring-downspectrometer
Aerodynecustombuilt
Aerodynecustombuilt
AerosolAE31filterabsorptionphotometer
AerosolAE31
AerosolAE31
AerosolAE33filterabsorptionphotometer
AerosolAE33
... further results

Category:Project

Category:Person Namespace User:


Form:User Template:User

Category:Section

Form:Section Template:Section

TODO:

  • Section overview
  • Section Members section


Category:Resource

Sub category:Category:Computational_Resource

Sub categories

Properties:

Category:Tutorials

Properties

Form:Tutorial Template:Tutorial

Marc's suggestions

1. **General announcements and recent updates section**: (CORE)

2. **Research section**: (CORE)

  - Research projects (planned, ongoing and closed) including descriptions, objectives, team members
  - Research resources (infrastructure, hardware, methodologies, best practices, data management, full list to be defined..)

Andre Castro (talk) 16:52, 7 March 2024 (CET) It does not make sense that hardware is subdued to Research resources. As there might be hardware, like some tools, that are not Research resources.

3. **Education Section**: (CORE)

  - CORE: Information on student project supervision (Bachelor, Master, PhD), grading rubrics, graduation ceremonies
  - Optional: Information about BsC and MSc programs in which GRS is involved
  - Optional: Course inventory with course code, content description and teaching teams
  - Optional: Resources for teaching, assessment tools, academic support services etc..

4. **Administrative Section**: (CORE)

  - CORE: Departmental policies, procedures, and guidelines related to HR, finance, facilities, and safety.
  - CORE: Contact information for departmental administrators, IT support, and other key personnel.
  - Optional: Guidelines for collaboration with industry partners, startups, or government agencies.
  - Optional: Forms and templates for travel requests, expense reports, equipment procurement, and event planning.

5. **Valorization, Outreach and Knowledge transfer Section**: (OPTIONAL)

  - Optional: Case studies or success stories highlighting the department's impact on industry, society, or policy.
  - Optional: Resources for intellectual property management, technology transfer, and commercialization strategies.

6. **Collaboration Tools**: (OPTIONAL)

  - Optional: List of people, with affiliation, expertise, roles/responsibilities and contact information
  - Optional: Discussion forums for brainstorming ideas, seeking feedback, and proposing improvements to the Wiki
  

7. **Technical Wiki Documentation** (CORE)

Notes & References