ShareDoc:PublicDocumentation/LODPlatform/DiscoveryInterface - Revision history

Anna at 10:07, 22 September 2025

2025-09-22T10:07:43Z

← Older revision		Revision as of 10:07, 22 September 2025
Line 25:		Line 25:
	* Embedded structured data. Each page will have embedded within its HTML markup a structured data description of the entity it represents. The description will consist of one or more JSON-LD encoded tags using the Schema.org vocabulary. This data will be utilised by search engines and others to provide enhanced listings and links, etc. This means that these collections will be more readily discoverable via popular search engines such as Google when users are seeking relevant information.		* Embedded structured data. Each page will have embedded within its HTML markup a structured data description of the entity it represents. The description will consist of one or more JSON-LD encoded tags using the Schema.org vocabulary. This data will be utilised by search engines and others to provide enhanced listings and links, etc. This means that these collections will be more readily discoverable via popular search engines such as Google when users are seeking relevant information.

	* Linked Open Data provision. Following Linked Open Data and web content negotiation principles, requests to the entity URI requesting RDF specific data formats such as (RDF-XML, Turtle, ~~Tripples~~, Quads, JSON-LD) will receive data in that form instead of HTML.		* Linked Open Data provision. Following Linked Open Data and web content negotiation principles, requests to the entity URI requesting RDF specific data formats such as (RDF-XML, Turtle, Triples, Quads, JSON-LD) will receive data in that form instead of HTML.

	'''Direct connections'''		'''Direct connections'''

Anna at 16:19, 30 July 2024

2024-07-30T16:19:49Z

← Older revision		Revision as of 16:19, 30 July 2024
Line 2:		Line 2:

	== Concept and art direction of the LOD Platform Entity Discovery Portal ==		== Concept and art direction of the LOD Platform Entity Discovery Portal ==
	The LOD Platform Entity Discovery Portal has been designed in a joint effort of the Share Family staff and member institutions, to respond to both patrons and library staff requirements and expectations, to reflect the components of the underlying data model infrastructure, and to provide an intuitive user experience.		The LOD Platform Entity Discovery Portal has been designed in a joint effort of the Share Family staff and member institutions, to respond to both patrons and library staff requirements and expectations, to reflect the components of the underlying BIBFRAME-based data model infrastructure, and to provide an intuitive user experience.

	It is designed to be easy to navigate. The structure and design of the system encourages browsing and exploring. The interface makes it quick and easy to jump from entity to entity until the user finds what they are interested in exploring.		It is designed to be easy to navigate. The structure and design of the system encourages browsing and exploring. The interface makes it quick and easy to jump from entity to entity until the user finds what they are interested in exploring.
Line 116:		Line 116:
	Each portal group has one “primary” portal. This is the non-branded version of the portal that represents the project as a whole, and not a particular institution or variation of the website. All other portals in a group are “secondary” or institutional portals (also informally called “skin portals” in Share Family jargon). The primary portal has certain minor differences compared to secondary portals. “Secondary” is the term used to configure features in the back-office, and in this context is synonym of “institutional”.		Each portal group has one “primary” portal. This is the non-branded version of the portal that represents the project as a whole, and not a particular institution or variation of the website. All other portals in a group are “secondary” or institutional portals (also informally called “skin portals” in Share Family jargon). The primary portal has certain minor differences compared to secondary portals. “Secondary” is the term used to configure features in the back-office, and in this context is synonym of “institutional”.

	For example: the primary portal of Share-VDE portal group is https://svde.org; institutional secondary portals are available for member institutions.		For example: the primary portal of Share-VDE portal group is https://svde.org; institutional secondary portals are available for member institutions, eg. https://nyu.svde.org.

	'''Single-portal portal groups'''		'''Single-portal portal groups'''

Anna at 15:18, 3 May 2024

2024-05-03T15:18:12Z

Anna at 15:17, 3 May 2024

2024-05-03T15:17:05Z

Show changes

Anna at 14:59, 3 May 2024

2024-05-03T14:59:53Z

Show changes

Anna at 14:45, 3 May 2024

2024-05-03T14:45:51Z

@@ Line 144: / Line 144: @@
 [[File:DiscoveryInterface 1714667280555.png|none|thumb|569x569px]]
@@ Line 150: / Line 151: @@
 Provide a text that is one single sentence, very short, and summarizes in non-technical terms why this website is relevant for the visitor.
 [[File:DiscoveryInterface 1714667324973.png|none|thumb|571x571px]]
@@ Line 156: / Line 158: @@
 On all subpages, a separate footer text appears which is slightly longer than the footer text on the front page. This text consists of two parts: Headline and Description (see illustration)For multi-portal groups, the footer text comes in two variations: one that is used on the primary portal and others that are used on all others (i.e. institutional/secondary) portals. The purpose of this distinction is, in the cases where it is relevant, to have a general project description on the primary portal, while on institutional portals, to be able to refer to the main portal as the representation of the underlying infrastructure — e.g. the main SVDE portal being referred to from all other SVDE portals (see illustration).
 [[File:DiscoveryInterface 1714667391214.png|none|thumb|575x575px]]
@@ Line 162: / Line 165: @@
 If you have alternative search engines that may be relevant to visit, you can provide links to these when no results are found via the portal group.
 [[File:DiscoveryInterface 1714667440565.png|none|thumb|588x588px]]
@@ Line 169: / Line 173: @@
 [[File:DiscoveryInterface 1714667505811.png|none|thumb|616x616px]]
 '''Information pages'''
 The information pages consist of two main sections:
@@ Line 176: / Line 181: @@
 As example, see Share-VDE information pages https://www.svde.org/about/about-share-vde
 [[File:DiscoveryInterface 1714667573096.png|none|thumb|588x588px]]
 __FORCETOC__

Anna at 16:33, 2 May 2024

2024-05-02T16:33:23Z

@@ Line 128: / Line 128: @@
 ==== Branding and design ====
 The branding of the primary portal (logo, header colour) is selected by the consortium / group of participating institutions. If consortium members / participating institutions have their own, branded version of the portal, the primary portal typically has the consortial branding.
 __FORCETOC__

Anna at 15:38, 2 May 2024

2024-05-02T15:38:57Z

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:LOD Platform Entity Discovery Portal}}
 == Concept and art direction of the LOD Platform Entity Discovery Portal ==
@@ Line 98: / Line 100: @@
 === Terminology and structure of Discovery Portals ===
 __FORCETOC__

Anna at 15:36, 2 May 2024

2024-05-02T15:36:34Z

← Older revision		Revision as of 15:36, 2 May 2024
Line 75:		Line 75:

	* Color themes, e.g. Dark theme		* Color themes, e.g. Dark theme

			== Configuration options ==
			This document presents the options available for configuring the Entity Discovery Portal part of the LOD Platform technology supporting the [https://www.share-family.org/ Share Family] environments.

			The configuration options of the Share Family discovery portals are designed to enhance the experience of end users navigating the linked data descriptions of the resources displayed, and are already applied to https://svde.org, https://pcc-lod.org, https://natbib-lod.org.

			This solution applies to both individual institutions, consortia or networks of institutions, and has been developed not only for general exploration purposes, but also to connect end users to local libraries’ / consortia services directly from the discovery portal of the Share Family environment. Therefore, the Entity Discovery Portal can be configured at several layers: for individual institutions, for a single consortium / group of institution, for a network of consortia.

			This process allows to seamlessly integrate the advanced linked data layer offered by the Share Family with the local library activities, and is independent of the ILS / LSP used by the institution.

			The configuration options described in this document refer to:

			* discovery portals structure;
			* branding and design;
			* textual content;
			* some specific functions.

			While this document presents the particular configurations of the discovery portals, the default functions of Share Family portals for exploring and for collaboratively editing the linked data exposed are extensively described in these guides (referenced at [[ShareDoc:PublicDocumentation/User guides\|https://wiki.share-vde.org/wiki/ShareDoc:PublicDocumentation/User_guides]]):

			* https://bit.ly/SFamily_discovery_portal_guide
			* https://bit.ly/SFamily_JCricket_guide

			=== Terminology and structure of Discovery Portals ===
	__FORCETOC__		__FORCETOC__

Anna at 13:02, 2 May 2024

2024-05-02T13:02:50Z

← Older revision		Revision as of 13:02, 2 May 2024
Line 10:		Line 10:
	=== Start anywhere — explore from there ===		=== Start anywhere — explore from there ===
	The user interface consists of two primary kinds of pages:		The user interface consists of two primary kinds of pages:

	'''1. Search pages'''		'''1. Search pages'''

Line 45:		Line 46:
	The art direction of is focused on two things: making linked data easy to understand and easy to use for library users. While maintaining simplicity in the UI, we guide the user through the complex data grid underlying the system.		The art direction of is focused on two things: making linked data easy to understand and easy to use for library users. While maintaining simplicity in the UI, we guide the user through the complex data grid underlying the system.

	In addition to keeping the UI simple, we have prioritized the following:		In addition to keeping the UI simple, we have prioritized the following:
	'''1. Conceptual data presentation'''
			'''1. Conceptual data presentation'''

	In general, we represent the entities in the UI in a way this intuitively makes sense. I.e. even if a certain piece of metadata technically belongs on the Item level, we may show it where relevant on the Instance level (e.g. physical location).		In general, we represent the entities in the UI in a way this intuitively makes sense. I.e. even if a certain piece of metadata technically belongs on the Item level, we may show it where relevant on the Instance level (e.g. physical location).

← Older revision		Revision as of 15:18, 3 May 2024
Line 1:		Line 1:
	{{DISPLAYTITLE:LOD Platform Entity Discovery Portal}}		{{DISPLAYTITLE:LOD Platform Entity Discovery Portal}}

	~~<big><span class="col-red">'''THIS PAGE IS WORK IN PROGRESS'''</span></big>~~

	== Concept and art direction of the LOD Platform Entity Discovery Portal ==		== Concept and art direction of the LOD Platform Entity Discovery Portal ==
Line 137:		Line 135:
	The default headline is a phrase indicating the main entities that can be searched: people (ie. contributors), original works (ie. the title of the resource in its most abstract sense), publications (ie. a publication of a work).		The default headline is a phrase indicating the main entities that can be searched: people (ie. contributors), original works (ie. the title of the resource in its most abstract sense), publications (ie. a publication of a work).
	[[File:DiscoveryInterface 1714748566153.png\|none\|thumb\|585x585px]]		[[File:DiscoveryInterface 1714748566153.png\|none\|thumb\|585x585px]]



Line 154:		Line 153:
	Provide a text that is one single sentence, very short, and summarizes in non-technical terms why this website is relevant for the visitor.		Provide a text that is one single sentence, very short, and summarizes in non-technical terms why this website is relevant for the visitor.
	[[File:DiscoveryInterface 1714748622278.png\|none\|thumb\|576x576px]]		[[File:DiscoveryInterface 1714748622278.png\|none\|thumb\|576x576px]]



Line 160:		Line 160:
	On all subpages, a separate footer text appears which is slightly longer than the footer text on the front page. This text consists of two parts: Headline and Description (see illustration)For multi-portal groups, the footer text comes in two variations: one that is used on the primary portal and others that are used on all others (i.e. institutional/secondary) portals. The purpose of this distinction is, in the cases where it is relevant, to have a general project description on the primary portal, while on institutional portals, to be able to refer to the main portal as the representation of the underlying infrastructure — e.g. the main SVDE portal being referred to from all other SVDE portals (see illustration).		On all subpages, a separate footer text appears which is slightly longer than the footer text on the front page. This text consists of two parts: Headline and Description (see illustration)For multi-portal groups, the footer text comes in two variations: one that is used on the primary portal and others that are used on all others (i.e. institutional/secondary) portals. The purpose of this distinction is, in the cases where it is relevant, to have a general project description on the primary portal, while on institutional portals, to be able to refer to the main portal as the representation of the underlying infrastructure — e.g. the main SVDE portal being referred to from all other SVDE portals (see illustration).
	[[File:DiscoveryInterface 1714748687310.png\|none\|thumb\|573x573px]]		[[File:DiscoveryInterface 1714748687310.png\|none\|thumb\|573x573px]]



Line 166:		Line 167:
	If you have alternative search engines that may be relevant to visit, you can provide links to these when no results are found via the portal group.		If you have alternative search engines that may be relevant to visit, you can provide links to these when no results are found via the portal group.
	[[File:DiscoveryInterface 1714748748657.png\|none\|thumb\|576x576px]]		[[File:DiscoveryInterface 1714748748657.png\|none\|thumb\|576x576px]]



Line 224:		Line 226:
	In a full-match search, the user is offered the option to expand the individual search to include partial matches; and if no full-match results are found for an individual search, the system will automatically re-submit the search to find partial matches and display those.		In a full-match search, the user is offered the option to expand the individual search to include partial matches; and if no full-match results are found for an individual search, the system will automatically re-submit the search to find partial matches and display those.
	[[File:DiscoveryInterface 1714748997932.png\|none\|thumb\|594x594px]]		[[File:DiscoveryInterface 1714748997932.png\|none\|thumb\|594x594px]]



Line 232:		Line 235:
	For some libraries, the focus may be to get the users directed to a physical location in the library as fast as possible. For these cases, it is possible to enable ‘quick items’ — a feature that shows item data directly in lists of publications, saving the user clicks when looking for a physical location. This option might be meaningful to enable together with the ‘publication simple search’ feature for some libraries.		For some libraries, the focus may be to get the users directed to a physical location in the library as fast as possible. For these cases, it is possible to enable ‘quick items’ — a feature that shows item data directly in lists of publications, saving the user clicks when looking for a physical location. This option might be meaningful to enable together with the ‘publication simple search’ feature for some libraries.
	[[File:DiscoveryInterface 1714749042305.png\|none\|thumb\|599x599px]]		[[File:DiscoveryInterface 1714749042305.png\|none\|thumb\|599x599px]]



Line 238:		Line 242:
	In case of data coming from a database shared by multiple institutions, showing the provenance is relevant as it gives evidence to the subjects contributed by the various institutions.		In case of data coming from a database shared by multiple institutions, showing the provenance is relevant as it gives evidence to the subjects contributed by the various institutions.
	[[File:DiscoveryInterface 1714749090547.png\|none\|thumb\|603x603px]]		[[File:DiscoveryInterface 1714749090547.png\|none\|thumb\|603x603px]]



Line 246:		Line 251:
	The example on the left shows a list of entities with alphabetic sorting enabled by default. The example on the right shows a list of entities with alphabetic sorting disabled by default.		The example on the left shows a list of entities with alphabetic sorting enabled by default. The example on the right shows a list of entities with alphabetic sorting disabled by default.
	[[File:DiscoveryInterface 1714749130635.png\|none\|thumb\|618x618px]]		[[File:DiscoveryInterface 1714749130635.png\|none\|thumb\|618x618px]]



Line 254:		Line 260:
	The link and the text of the action button can be configured.		The link and the text of the action button can be configured.
	[[File:DiscoveryInterface 1714749172071.png\|none\|thumb\|628x628px]]		[[File:DiscoveryInterface 1714749172071.png\|none\|thumb\|628x628px]]



Line 277:		Line 284:
	On the front-page of the portal a link to the main library website can be added; URL and label can be configured.		On the front-page of the portal a link to the main library website can be added; URL and label can be configured.
	[[File:DiscoveryInterface 1714749288721.png\|none\|thumb\|590x590px]]		[[File:DiscoveryInterface 1714749288721.png\|none\|thumb\|590x590px]]



Line 289:		Line 297:
	Technical specifications for the logo will be provided.		Technical specifications for the logo will be provided.
	[[File:DiscoveryInterface 1714749341462.png\|none\|thumb\|608x608px]]		[[File:DiscoveryInterface 1714749341462.png\|none\|thumb\|608x608px]]


	If the portal is under development, it’s possible to enable the ‘beta badge’ feature.		If the portal is under development, it’s possible to enable the ‘beta badge’ feature.