Re3gistry: Your interoperable open source tool for managing and sharing reference codes
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 351 | |
| Author | ||
| Contributors | ||
| License | CC Attribution 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/69039 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language | ||
| Production Year | 2022 |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
| |
| Keywords |
FOSS4G Firenze 2022205 / 351
1
7
13
22
25
31
33
36
39
41
43
44
46
52
53
55
58
59
60
76
80
93
98
104
108
127
128
133
135
141
142
143
150
151
168
173
176
178
190
196
200
201
202
204
211
219
225
226
236
242
251
258
263
270
284
285
292
00:00
Open sourceCodierung <Programmierung>James Waddell Alexander IIWindows RegistryArchitectureRevision controlSystem identificationElectronic mailing listMachine codePhysical systemDigital rights managementSelf-organizationEndliche ModelltheorieExtension (kinesiology)Interface (computing)Computer-assisted translationDigital signalArchaeological field surveyLinked dataComputer-generated imageryFinitary relationQuery languageOracleTomcat <Programm>Uniform resource locatorSystem administratorSign (mathematics)Data structureLoginContent (media)InformationBenutzerhandbuchStandard deviationGroup actionField (computer science)Zirkulation <Strömungsmechanik>Cache (computing)Configuration managementElectronic visual displayComputer configurationControl flowState of matterFormal languagePlanningPortable Object AdapterFrequencyElement (mathematics)Instance (computer science)Cumulative distribution functionHypermediaFile formatGeneric programmingSoftwareMessage passingInformation securityStrategy gameDrop (liquid)Menu (computing)Inheritance (object-oriented programming)Component-based software engineeringConsistencyNumberCore dumpAuthenticationFormal grammarRouter (computing)FreewareWeb applicationNetwork topologyJava appletScripting languageInstallation artHuman migrationSubject indexingDisintegrationOpen setMultiplicationLatent heatUser interfaceSoftware developerIterationComa BerenicesPlastikkarteComputing platformCone penetration testRepository (publishing)GoogolMereologyWikiSoftware testingSearch engine (computing)Error messageAttribute grammarVideoconferencingExplosionPresentation of a groupSoftwareWindows RegistryGame controllerMachine codeElectronic mailing listWeb applicationComponent-based software engineeringOpen sourceDebuggerOrder (biology)Different (Kate Ryan album)Enumerated typeMathematicsMultiplication signValidity (statistics)Connected spaceCartesian coordinate systemInformationPlug-in (computing)Java appletField (computer science)Revision controlFront and back endsFile formatSystem administratorElectronic visual displayTwitterComputer configurationGroup actionGreatest elementTouchscreenAdaptive behaviorLatent heatGraph coloringTemplate (C++)Default (computer science)1 (number)Computer programmingUser interfaceProcedural programmingCentralizer and normalizerStudent's t-testService (economics)Moment (mathematics)DampingBitState of matterFunctional (mathematics)Presentation of a groupFeedbackData modelPhysical systemIdentifiabilityRaw image formatElement (mathematics)Content (media)Search engine (computing)Wave packetLattice (order)Mobile appDescriptive statisticsWeb pageFormal languageTraffic reportingEmailMereologyAddress spaceSoftware testingVirtual machineDigitizingComputing platformSoftware developerLevel (video gaming)DatabasePoint (geometry)Form (programming)Computer fileInternationalization and localizationPublic domainOpen setSelf-organizationProfil (magazine)Semantics (computer science)Computer programBootstrap aggregatingServer (computing)Digital rights managementRepository (publishing)Decision theoryINTEGRALStandard deviationGraph (mathematics)AdditionInsertion lossMetropolitan area networkCompilation albumWeb 2.0Single-precision floating-point formatLink (knot theory)LoginArchaeological field surveySoftware maintenanceWebsiteMeasurementSlide ruleNumeral (linguistics)Numerical taxonomyBootingComputer animation
Transcript: English(auto-generated)
00:00
Thank you very much. So my name is Jordi Scriva and I will be giving this presentation on the registry software together with Juan Martín Pelegrina from Bilbo Mántica which is one of the contractors that is helping us to push this project forward. So the InSPARE registry is one of the InSPARE central components together with the InSPARE
00:24
registry portal and the InSPARE reference validator and we are now pushing to maintain all these projects which are open source by the community and also pushing
00:46
for sustainable connections with OGO. So I will be just introducing the presentation and then I will pass the floor to Juan in order to introduce the technical details of the project and our activities on community engagement.
01:03
So what is a registry? The registry is a container or reference code so the idea is to identify a list of things. These things could be code lists, enumerations, the difference
01:27
is that code lists are extensible, enumerations are not, taxonomies, control vocabularies, glossaries, et cetera, so the idea is to manage the changes of these items over time. This is the concept of versioning so that you are able to reference any of the versions
01:44
of these items and check between them the differences that have been registered in the registry. The registries are useful in order to avoid common mistakes like for
02:02
example entering synonyms of a concept or misspellings when filling out online forms or even XML files for example. Facilitates also the internationalisation of the user
02:20
interfaces by providing multilingual levels so any of the descriptions of these items could be translated into different languages and all these elements are also registered as part of the content of the database and this is really useful to ensure semantic
02:41
interoperability when exchanging data between systems and applications. So the idea is to increase the value of these reference codes when they are widely used and referenced by the community. So the registries software is a system of registers so allows sharing
03:07
this and management of these reference codes through the use of persistent URIs or persistent identifiers which are governed in a consistent manner so any of the items
03:21
that are considered in the database are referenced by persistent identifier and you can point these elements in your work. So it provides the central access points where these levels and reference codes descriptions are easily accessible by both humans or machines
03:43
so it's not only something in the database but you can also browse all these items and the descriptions in a front-end. And as I said, Foster Semantic and Organisation Interoperability. The registry has been funded by the ARENA and ELIS actions and
04:04
more recently it has been also included within the digital Europe funding programme and the idea is to get this software, the registry within the common service platform
04:21
which is in this digital action. You can find more information in the link below. And it's also important to say that the use of the registry is not only for geospatial SDIs but it could be reduced in any domain including geospatial so it should
04:46
not be necessary to have a geospatial domain so you can reference it in any of the domains that you would have these needs. And finally, about the Federation tool. This is another additional component associated
05:08
to the registry where the national extensions to the national registers can be browsed in a single place. This was worn as a test for bringing this national extension of
05:27
InSPER data models in a single place and the idea is that the content of all these extensions and different registers are, let's say, introduced in a kind of a decade application
05:45
profile format which is the raw format in order to make them ready to use browsable and browsing in such kind of application. The idea is to make different uses to access
06:06
these extensions in an easy way. Also, this component could be also reused like the registry and yes, could be also customized in the front end. And I will give the floor to Juan
06:31
which will continue. Okay, thank you Jordi. Well, as Jordi was saying, I am one of the project managers of this project. I am here on behalf of a consortium of three companies, Guadal del
06:46
Ambulómática from Spain and Epsilon Italia. And also I have to say that our technical leader unfortunately hasn't been able to fly here because of an illness. So I'm going to try to give you a brief overview about the registry, the functionalities in 15 minutes.
07:03
So as you all know, the registry is an open source solution. It's a Java application that is using a Postgres SQL database but can be adapted to use different kind of databases and also the search engine is solar. That is for the back end and the front end is
07:28
a bootstrap and JavaScript on an Apache server. So there are three main components, three parts of the registry that are the back end that is the administrator side of
07:45
the registry and then all the information of the back end is available on the IPI and then there is a front end that is for the user to visualize what is provided in the IPI.
08:02
So the functionalities of the back end which is the administrative side, administrative component of the registry is you need to log in, has the log in functionality and then according to the role that you have because there are different roles, you will see one
08:24
dashboard or other dashboard. As Jordi was saying, the main purpose of the registry is manage content. So it allows you to create, modify, delete items. Also, it's quite important
08:42
because it's keeping the versioning of the items that you are updating or you are even deleting and most of them are accessible and it's multilingual. In addition, for managing the content, the registry is already having implemented a workflow according to the
09:06
standard, to the ISO standard. That is the workflow that you can see is the one of the standards where there is a draft, you submit the draft that can be accepted or not and then if it's accepted, it's valid, then publish it not, can be accepted with changes, go back to
09:22
the graph and also the draft, the proposal can be not affected. So we are still talking about the C admin, the back end that have several functionalities. One of them is that
09:40
you can configure the display, the setting. So you can add if you want or you need it, new fields to the item or you can delete the field that already have, you can change the color, the display of everything that you want in order to be more suitable for you,
10:06
for your purpose. As we were saying before, the workflow is well-defined because it's the one of the ISO with the following roles, submitting organization, control body, register manager and registry manager. This is the only workflow that actually is implemented in the
10:27
registry as it is. We are currently working to try to implement new workflow where an easy workflow, a simplified workflow. So you will have the option to use the one from the ISO or
10:44
even to go to the simplified one or even to design or to propose a new workflow. So these are the, this is the workflow with the different dashboard. You can see the dashboard for submitting organizations, then with the different action that can be, you submit the
11:06
item that you want to add to that registry, then the control body has to make a decision what to do with this specific item and the ones that is approved is the registry, register manager, the one who has to publish it. So that we have finished mainly
11:27
with the main functionalities of the admin side, the backend as we call it, and all of this information is available through an API. So the API you can search by URI, by ID and by
11:42
ID and status. We are also currently working on this, have been trying to, improving the API in order to adapt it to the open API specification. Then you have the front end also has some functionalities. The front end you can adapt the front end to the template,
12:08
the colors of your organization, or you can go to the template that we have by default that are the ones that we can see at the bottom of the screen. For example, in this slide, you can see the adaptation that they are doing here in Italy that is for the expired Italy
12:27
registry that they are already using this software. They are using registry software to provide the expired registry. They are currently using version 2. Also, the front end,
12:42
the registry has different formats available and allows you to add new formats. So you can decide if you want to provide new formats. Then as you know, and I already said, this is an open source project. You can find all the code, all the documentation on GitHub,
13:05
under the organization of European Commission and GRC, under the project registry, and also on OSC geolive. The registry software was included in OSC geolive 14, and this year
13:24
is going to be still there. So the latest stable version can be found in OSC geolive 15 under the folder where services. If you want to start playing around to use it, you just need to click on the registry start desktop. Then how to install it. There are two
13:43
ways at the moment to install the application. So you can download the precompiled application that has been compiled using Java. It's already on the manual and all the precompiled
14:01
application is on GitHub. Even if you want, it's quite easy to do. You can download the software and you can compile your own application. So this is for the IPI and the back end, the system and the front end, and I said at the beginning, it's a web app that is available in the mentioned repository. Both, it doesn't matter the way that you choose, but it's going
14:26
to direct you to the installation. It's quite easy and simple to follow. There are two types of installation. You can do a new installation from scratch or you can migrate from the latest older version of the registry software. I'm going to speed up a little bit.
14:46
Even more, so who is using it at the moment is mostly used by public sector. The European Commission is using it. The spy registry is using registry software. And there are a few members of the state who are using the registry. Only Italy and Slovakia are using
15:07
the version 2 of the registry. And as Jordi was commenting at the beginning, it can be used by the private sector because it can be added and the format doesn't have to be special information, the one that you can manage with the registry. This is a summary
15:25
of the functionalities that I've been telling you for the next release that we are working on. We are working on providing a new way to install the registry software through docket installation. We want to simplify the workflow and we want to improve the open
15:42
the IPI, the integration with the registry of registry. And of course, we are working on the issues that have been detected by us and the community. And the next release is meant to be ready by the end of September. This is the release plan that is available on GitHub.
16:01
And this is what is important for us. We want the community. We want you, the user, we want you to become a user if you are not. But we want your feedback. We would like to hear and to help us to improve the tool. You can do it, as you probably know, using opening usage on GitHub, on the repository and also we have the discussion tab for
16:26
suggestion and enhancement. And we have a procedure that is already explained on the GitHub repository how to contribute. And then this has something important for us because we managed for last summer to be included on the Google Summer of Code 2022 program
16:47
because as a guest project, unfortunately we didn't have any students because we did it quite late anyway and we managed to get it. But we are going to be next year. So if any of
17:01
you or in any of your organization you are using registry and using that, you know, someone that can collaborate and want to be involved in Google Summer of Code next year, please start playing with the code because as we already know, if you start developing,
17:22
it's much easier to your application to be affected for this program. Then the future plans for the registry. We want to carry on improving the project, solving all the issues that we have detected. We want to hear from the community. For this reason,
17:44
we are submitting Sootbase. Sootbase will be available on GitHub quite soon. And we would like to support the user and the developer of feeding them training, training course. There will be training material available. It's already on the join app page that Jordi
18:04
mentioned at the beginning. And also we want to strengthen the community that we are building around this software. And in addition, we want to do the integration with the registry tool, the registry of register. Just to finalize the conclusion is that the registry
18:28
software is active project. It's active development. We already have a well defined roadmap for the next three years. And it's going to carry on for more years. It's open
18:44
development. All the information is on GitHub and is open to all of you. And we are open to hear you. And everyone can be engaged as part of the registry community. Not only developer. Yes. Reporting issues. Proposing improvements. And even if facing
19:05
and development will be perfect. So, thank you. Thank you for your time. If you want to contact us, there are our email addresses and our Twitter. So this is the Twitter of our technical leader and Jordi. Okay. Thank you.