DynamicalSystemsGroup/koi

jdd-kami - Overview

jdd-kami has 4 repositories available. Follow their code on GitHub.

GitHub - BlockScience/koi-net: Implementation of Knowledge Organization Infrastructure Network (KOI-net) protocol in Python

Implementation of Knowledge Organization Infrastructure Network (KOI-net) protocol in Python - BlockScience/koi-net

jcsalterego - Overview

jcsalterego has 53 repositories available. Follow their code on GitHub.

flo-bit - Repositories

building things for the web svelte/threlte/threejs/astro/atproto - flo-bit

Role Based Repositories

Monorepo or Multirepo? Role-Based Repositories

dholms.at/opensocial-group

A repository on Tangled

kjaanson.eurosky.social/atproto-exploration-tooling

Small codebase to explore and build helper tooling for ATProto research. Mostly for my own use.

What is an atproto repository? - The Book of Eli

One repo with multiple ways to sync

The Gradual Merging of Repository and CRIS Solutions to Meet Institutional Research Information Management Requirements

Much has been said in recent times about the alleged dichotomy between Institutional Repositories (IRs) and Current Research Information Systems (CRISs). According to this highly ideological argument, IRs would be the platforms to support the non- commercial initiative jointly carried out by HEIs – and specifically their Libraries – in order to freely disseminate their research outputs, whereas CRISs would support the whole institutional research information management (RIM) with special emphasis on projects and funding. RIM being an activity oriented towards reporting for research assessment exercises and thus tightly connected to the institutional funding, the support from the Management at HEIs for CRIS implementation and operation and for the Research Office traditionally in charge of such tasks would be much higher than for the much less relevant IR. Moreover, the awareness of researchers and scholars towards such platforms will usually be much higher for the CRIS – from whose accurate and complete depiction of their research activity their salaries will ultimately depend – and it won’t be unusual to collect complaints on the need to ensure that both systems are simultaneously fed with the appropriate, often duplicated information. According to this conception, it is often hard to get the institutional Research Office and Library to work together for improving the end-user experience by enhancing their system interoperability. While much of this may still be happening at a number of HEIs, the general landscape is swiftly evolving and it's not that accurate anymore to describe the RIM system configuration at institutions in such oversimplified terms. CRIS/IR interoperability is now a fairly widespread feature that will allow both platforms to efficiently exchange information and reinforce each other's features, and especially the borders between what each of these platforms is and does are becoming increasingly blurred. Commercial CRISs are gradually becoming compliant with the OAI-PMH protocol and thus becoming able to offer institutions an integrated repository functionality, while the main open source IR platforms have now developed extended data models that will allow them to deliver features traditionally associated to CRISs such as project and funding management, hence becoming suitable solutions for research institutions where purchasing or developing a highly-sophisticated CRIS is not a top priority. This paper aims to describe the areas where CRIS/IR interoperability is taking place, and will provide a set of use cases for institutional research information system configuration involving IRs, CRISs and a combination of both. These will show how both systems are now increasingly merging for best serving institutions and their researchers.

KOI-net Protocol Specification Draft v1.0

The KOI-net protocol defines the standard communication patterns and coordination norms needed to establish and maintain Knowledge Organization Infrastructure (KOI) networks. KOI networks are heterogeneous compositions of KOI nodes, each of which is capable of autonomously inputting, processing, and outputting knowledge. The behavior of each node and configuration of each network can vary greatly; therefore, the protocol is designed to be a simple, flexible, and interoperable foundation for future projects to build on. The protocol only governs communication between nodes, not how they operate internally. As a result we consider KOI-nets to be fractal-like, in that a network of nodes may act like a single node when viewed from outside.