Project

geolexica-server

0.0
There's a lot of open issues
No release in over a year
geolexica-servergeolexica/geolexica-serverHomepageDocumentationSource CodeBug TrackerWiki
Server for Geolexica sites
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
1,490
Stars
2
Forks
1
Watchers
7
 Releases
Current version
0.0.1
Total releases
2
First release
2022-09-28
Latest release
2022-09-28
 Issues
Open Issues
41
Closed Issues
48
Total Issues
89
Issue Closure Rate
53%
 Pull Requests
Open Pull Requests
0
Closed Pull Requests
2
Merged Pull Requests
105
Pull Request Acceptance Rate
98%
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2022-07-10
Reverse Dependencies
1

 Dependencies

Development

bundler
~> 2.1
pry
>= 0
rake
>= 10
rspec
~> 3.9

Runtime

jekyll-geolexica
>= 0
mercenary
>= 0
relaton
>= 0
zeitwerk
~> 2.4
 Project Readme

ISO/TC 211 Geolexica Terminology Database

Build Status

Build Status

Build Status

Introduction

Geolexica is the site name of the online version of the ISO/TC 211 Multi Lingual Glossary of Terms.

This repository contains the source of the https://www.geolexica.org site.

The site is managed by the ISO/TC 211 TMG together with Ribose.

Note
 This repository is only meant for internal consumption!

How to add/remove entries or suggest changes?

For change suggestions, contact ISO/TC 211 TMG.

This terminology database is managed by the ISO/TC 211 TMG, and it only considers requests from within ISO/TC 211. The database is not directly community-managed or community-sourced.

ISO/TC 211 MLGT component overview

Components involved in ISO/TC 211 MLGT solution:

  1. Geolexica.org: this repository. Renders Geolexica database into HTML, JSON-LD and other Web-friendly formats.

  2. Geolexica database: see geolexica/geolexica-database. Hosts all concept data in YAML; bundles facilities for converting authoritative spreadsheet data into YAML. Candidate to become authoritative source, contingent upon factual usage of Glossarist by TMG.

  3. Manually managed XLST spreadsheets (1.0 workflow): see ISO-TC211/mlgt-data. Currently the authoritative source in 1.0 workflow. Will be phased out in favor of Geolexica database in 2.0.

  4. Glossarist desktop application (2.0 workflow): see geolexica/geolexica-desktop. Will be used to manage the Geolexica database in 2.0 workflow.

Change lifecycle (1.0, current)

  1. Requested changes are directed to ISO/TC 211 TMG.

  2. When a change is approved, TMG publishes a new version of ISO/TC 211 “Multi-Lingual Glossary of Terms”.

  3. TMG uploads the new MLGT version to mlgt-data repository.

  4. From the updated mlgt-data, a new snapshot of the database is created in geolexica-database repository.

  5. After new snapshot of the database is committed to geolexica-database, ISO/TC 211’s Geolexica.org is deployed with the latest database version.

Change lifecycle (2.0, near future)

  1. Requested changes are directed to ISO/TC 211 TMG.

  2. Adding, updating, approving concepts & terms in ISO/TC 211 Geolexica database is done by TMG using the desktop application under development.

  3. As changes are made, new versions of Geolexica database are created, and ISO/TC 211’s Geolexica.org is deployed with the latest database version.

Internal operations

Note
 These steps are only intended for the internal operator of the site!

Building the site

  1. Ensure geolexica-database submodule is up-to-date.

  2. Run make _site

Deployment

Please push all changes to the staging branch, and changes will be automatically deployed and reflected on the staging site.

If your changes are to be made public to the production site, please contact Ribose.

Rendering of HTML

Jekyll is used to render YAML into HTML.

Note
 Since Jekyll Collections have this flaw where YAML files can’t be directly rendered, a hack is implemented in the Makefile _concepts target, so that every YAML file is converted into AsciiDoc by padding --- at the end.