-
Notifications
You must be signed in to change notification settings - Fork 2
Data Hub
A Data Hub is a front end to a LA portal, its main goal is to show a subset of the whole data.
The subset of data can be split by region, taxonomy, basisofrecord (specimen only), temporal lapse or by any other query.
A display of a subset is a Hub. Hubs can be regional, taxonomic and thematic (depending on how the data is split).
One LA portal can have a lot of Hubs, each of them focused on different data and environnements: one can be about the data inside a specific region, an institution (like an Herbarium), another can show the data about a species in the 20s, et cetera.
Hubs can have differents active modules inside them, each of them are independant from the others (at least on the front-end).
Notable examples of hubs:
- ALA hub of The Australasian Virtual Herbarium
- ALA hub of Murray-Darling Basin Authority
- ALA hub of Online Zoological Collections of Australian Museums
- UK NBN Atlas has 4 regional portals: NBN Atlas Northern Ireland, NBN Atlas Scotland and NBN Atlas Wales.
- GBIF Togo
Biocache (records) and BIE (species pages) are used as query context; they can be configured in externals configuration files:
- Biocache:
/data/ala-hub/config/ala-hub-config.properties
- BIE:
/data/ala-bie/config/ala-bie-config.properties
Demo queries in the biocache can be made with dq=
.
BIE load Darwin Core Archive (DwCA) and can be extensible, support for adhoc fields and for the "Distribution" extension exist. Example of a query on BIE : fq=distribution:Scotland
You can create a different branding for each of your hubs so can be different from you LA main branding. Also probably you'll use a different domain or subdomain from the institution that hub will belongs to (some local community or some herbarium, etc).
For details about styling see Styling the web app.
In the collectory admin interface look for the View all data hubs option, here you can add a new DataHub. Edit the name and any other information you required.
In the Members section add the identifier of the Institutions, Collections and Data Resources that belong to the Hub. This is the information that will actually show in the web app.
Find the UID of the hub you already created in the Collectory admin interface. In the web app config file (grails-app/conf/config.groovy) add the property with the appropiate UID.
biocache.queryContext = "data_hub_uid:dh1"
Or via ala-install
inventory:
enable_query_context = true
biocache_query_context = data_hub_uid:dh6
Now we need to "mark" which records belongs to that datahub. For this we need to ingest again the data resources that form part of this datahub. At the end, in cassandra field dataHubUid_p
should contain your dh1
hub id after processing. Similarly in solr
the data_hub_uid
should containt dh1
after indexing.
The config variables starting with facets.
are responsible for this:
-
facets.include
- comma separated list of fields to include (usually only those fields not in the default set as specified by${biocache.baseUrl}/search/facets
) -
facets.exclude
- comma separated list of fields to exclude. i.e. fields in the default set you don't want to appear -
facets.hide
- comma separated list of field that would be included in the facet column, that you want to be hidden (i.e. un-ticked in the "customise filters" drop down menu). These fields will be displayed if the user changes the default display settings and chooses to turn them on.
Note, you can also change the default set of facets but this is set in the biocache-service application, also via config vars (I think). You may also want to change the way facets are grouped together (see ${biocache.baseUrl}/search/grouped/facets
).
As you will request data from your main LA deployment, you'll need to allow your new hub domain to access to your main LA biocache.
See this page for info about hubs customizations.
For more technical information, see section 2.6 Data Hub on the ALA Key Technical Documentation (English).
Index
- Wiki home
- Community
- Getting Started
- Support
- Portals in production
- ALA modules
- Demonstration portal
- Data management in ALA Architecture
- DataHub
- Customization
- Internationalization (i18n)
- Administration system
- Contribution to main project
- Study case