Advanced search
ABR - BRegDCAT-AP Tools
This solution is dedicated to provide information on open source tools that ABR team created to support Member States (MS) in implementing the BRegDCAT-AP specification / data model. Overview of tools…
SOLUTIONCreated: 16/10/2020
ABR - BRegDCAT-AP
This solution is dedicated to an application profile of DCAT-AP for base registries, namely, BRegDCAT-AP, aiming to provide a standard data model / specification for base registries access and…
SOLUTIONCreated: 27/03/2019BRAIF - Share your opinion on Framework now !
#ABR Team invites data management experts, policy makers and other interested parties to share their view on the ?Framework on Base Registries Access and Interconnection - #BRAIF. This Framework aims to provide guidance to Member States (MS) on how to grant access to the data in base registries (BRs…
DISCUSSIONCreated: 15/06/2020BRAIF - Framework - Your opinion on Data and Technical Architecture
The Framework on Access to Base Registries (BRAIF) and Interconnections aims to provide guidance to Member States on how to grant access to the data in Base Registries and how to interconnect them. Technical Architecture A service-oriented architecture is composed of services that are self-contained…
DISCUSSIONCreated: 08/10/2019BRAIF - Your opinion on Data Governance, Quality, Security
The Framework on Access to Base Registries (BRAIF) and Interconnections aims to provide guidance to Member States on how to grant access to the data in Base Registries and how to interconnect them. Data Governance Its implementation requires primarily the following aspects: organisational structures…
DISCUSSIONCreated: 08/10/2019BRAIF - Framework - Your opinion on Metadata Management
The Framework on Access to Base Registries (BRAIF) and Interconnections aims to provide guidance to Member States on how to grant access to the data in Base Registries and how to interconnect them. METADATA MANAGEMENT Why do we do metadata management? To provide organisational understanding of…
DISCUSSIONCreated: 04/10/2019BRAIF - Framework - Your opinion on Master Data Management
The Framework on Access to Base Registries (BRAIF) and Interconnections aims to provide guidance to Member States on how to grant access to the data in Base Registries and how to interconnect them. Master Data Management With regard to master data management, we propose to focus on improving data…
DISCUSSIONCreated: 03/10/2019BRAIF - Framework - Your opinion on the proposed conceptual model
The Framework on Access to Base Registries (BRAIF) and Interconnections aims to provide guidance to Member States on how to grant access to the data in Base Registries and how to interconnect them. Strategy 1.The BRAIF helps enabling Base Registry access, interconnection and integration 2.It defines…
DISCUSSIONCreated: 03/10/2019SYN-48 Possible inconsistencies when aggregating fragments
In specific cases, consuming a snapshot with sequence number n and the subsequent fragments (n+1,.., n+m) leads to different foreign data in the MIDB than consuming the snapshot n+m. Clarification: this occurs when fragments do not hold all information about the entity that has been updated. E.g…
DISCUSSIONCreated: 18/12/2012SYN-47 Explicit Subscription for Notifications
In release 2.0, the Syndication Interface module sends notifications about new fragments or snapshots to all Syndication modules in the local copy of the SPOCS TL. As documented in D1.4 Software Architecture Description, version 2.0, Section 3.2.2, Ad 1, it would be beneficial to include an explicit…
DISCUSSIONCreated: 18/12/2012SYN-46/ESE-47 Consolidated Configuration
The modules of release 2.0 use multiple configuration files. They also use part of the syndication database for configuration. Consolidating configuration in just one or two managed objects would simplify system management. Component Code Category improvement
DISCUSSIONCreated: 18/12/2012ESE-46 More Robust Retry Mechanism for Sending Notifications Remotely
The WP4 routing library that the Syndication Interface module uses for sending notifications to remote Aggregation modules simply writes failures to deliver these notifications into a retry file. The implementation of release 2.0 does not use this information to try to re-send the notifications…
DISCUSSIONCreated: 18/12/2012