Share-VDE - Recent changes [en]

ShareVDE:Main Page/SVDE institutions

Anna — Thu, 16 Jul 2026 10:46:23 GMT

← Older revision		Revision as of 10:46, 16 July 2026
Line 13:		Line 13:

	*Berkeley Law Library [https://www.law.berkeley.edu/library/ www.law.berkeley.edu/library/]		*Berkeley Law Library [https://www.law.berkeley.edu/library/ www.law.berkeley.edu/library/]
			*Brandeis University https://www.brandeis.edu/
	*Duke University [http://www.duke.edu/ www.duke.edu]		*Duke University [http://www.duke.edu/ www.duke.edu]
	*Lehigh University [https://www1.lehigh.edu/ www1.lehigh.edu]		*Lehigh University [https://www1.lehigh.edu/ www1.lehigh.edu]

ShareFamily:Resources

Anna — Wed, 15 Jul 2026 17:45:57 GMT

← Older revision		Revision as of 17:45, 15 July 2026
(2 intermediate revisions by the same user not shown)
Line 43:		Line 43:

	==Bibliographic references==		==Bibliographic references==
			''BDIB: the first Bibliographic Database of Interactive Books'', by Gianfranco Crupi, Annalisa Di Sabato, Alice Guercio, Michela Giacomelli, in «Digitalia», v. 21 n.1 (2026) https://doi.org/10.36181/digitalia-00159.

	''New Pathways for Resource Description and Interoperability: Innovative Strategies from the Share Family Ecosystem'', by Nina Servizzi, Tiziana Possemato, Jeanette Norris, Sebastian Hammer, in «Charleston Conference Proceedings, 2024», 298-314 (2025) https://doi.org/10.3998/mpub.13235636.		''New Pathways for Resource Description and Interoperability: Innovative Strategies from the Share Family Ecosystem'', by Nina Servizzi, Tiziana Possemato, Jeanette Norris, Sebastian Hammer, in «Charleston Conference Proceedings, 2024», 298-314 (2025) https://doi.org/10.3998/mpub.13235636.

Line 92:		Line 94:

	=== Year 2026 ===		=== Year 2026 ===
	''[https://wiki.share-vde.org/w/images/b/b7/Full_presentations_Share_Family_Workshop_ALA_2026-Jun-29.pdf Share Family Workshop]'', at ALA Annual, June 30 2025, by Jill Morris, Sebastian Hammer, Tiziana Possemato, Anna Lionetti; [https://youtu.be/EcZwWQoRJKw recording available].		''[https://wiki.share-vde.org/w/images/b/b7/Full_presentations_Share_Family_Workshop_ALA_2026-Jun-29.pdf Share Family Workshop]'', at ALA Annual, 29 June 2025, by Jill Morris, Sebastian Hammer, Tiziana Possemato, Anna Lionetti; [https://youtu.be/EcZwWQoRJKw recording available].

	[https://wiki.share-vde.org/w/images/7/70/LC_BF_Forum_January-2026_static_version.pptx.pdf ''BIBFRAME in Practice: Powering a Collaborative Share Family Community with JCricket''], at LC BIBFRAME Update Forum, 9 February 2026, by Tiziana Possemato and Anna Lionetti; [https://www.loc.gov/bibframe/news/bibframe-update-feb2026.html materials and recording available].		[https://wiki.share-vde.org/w/images/7/70/LC_BF_Forum_January-2026_static_version.pptx.pdf ''BIBFRAME in Practice: Powering a Collaborative Share Family Community with JCricket''], at LC BIBFRAME Update Forum, 9 February 2026, by Tiziana Possemato and Anna Lionetti; [https://www.loc.gov/bibframe/news/bibframe-update-feb2026.html materials and recording available].

ShareVDEmembers:DevelopmentProcess

Serena Cericola — Wed, 15 Jul 2026 10:20:19 GMT

ShareVDE:Activities

Anna — Fri, 10 Jul 2026 10:00:45 GMT

← Older revision		Revision as of 10:00, 10 July 2026
Line 28:		Line 28:
	Also, each community of institutions participating in the individual Share Family of initiatives can establish its specific governance group that determines the policy for the treatment and processing of the data.		Also, each community of institutions participating in the individual Share Family of initiatives can establish its specific governance group that determines the policy for the treatment and processing of the data.

	=== Consortia and networks of institutions ===		=== [https://wiki.share-vde.org/wiki/ShareVDE:Activities/Consortia Consortia and networks of institutions] ===
	Ongoing conversations with consortia representatives are underway to define the configurations of this innovative collaboration. As an example of this effort, the [https://bit.ly/SF-Executive-Summary-Consortia Share Family Executive Summary for Consortia] offers additional insights into how the Share Family can assist consortia in transitioning to linked open data, providing valuable strategies and support. Approved by our Advisory Council, the document emphasizes Share Family’s pivotal role in aiding consortia in adopting linked data methodologies for enhanced collaboration. The Share Family aims to empower consortia with the tools and knowledge necessary to seamlessly integrate linked open data principles, fostering innovation and interoperability within consortia networks.		Ongoing conversations with consortia representatives are underway to define the configurations of this innovative collaboration. As an example of this effort, the [https://bit.ly/SF-Executive-Summary-Consortia Share Family Executive Summary for Consortia] offers additional insights into how the Share Family can assist consortia in transitioning to linked open data, providing valuable strategies and support. Approved by our Advisory Council, the document emphasizes Share Family’s pivotal role in aiding consortia in adopting linked data methodologies for enhanced collaboration. The Share Family aims to empower consortia with the tools and knowledge necessary to seamlessly integrate linked open data principles, fostering innovation and interoperability within consortia networks.

ShareDoc:The PostMan Collection

Massimiliano Branca — Fri, 03 Jul 2026 13:03:09 GMT

← Older revision		Revision as of 13:03, 3 July 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:How to import the Share-VDE API Collection: the PostMan Collection}}		{{DISPLAYTITLE:How to import the Share-VDE API Collection: the PostMan Collection}}

	The ~~following link~~: https://~~www~~.~~getpostman~~.~~com~~/~~collections~~/~~bd55c075725e90383779 points to a collection of API examples that can be imported in PostMan<ref>~~<~~nowiki~~>https://~~www~~.~~postman~~.~~com<~~/~~nowiki>~~</~~ref~~> ~~using~~ the ~~steps described below~~.		The Postman collection has been updated: login via environment variables (no embedded credentials), a consistent environment, and extended coverage of all read-only calls (REST and GraphQL).

			To use it:
			#Import the collection and the UAT environment (both attached to this page).
			#In the environment, set the API address (<code>https://uat-mt.api-gw.svde.org</code>), the login/IdP
			address (<code>https://uat-mt.idp.share-family.org/auth/realms/svde</code>) and your own credentials.
			#Run the login request first to obtain a token; the other requests reuse it automatically.

	The examples you'll find in the collection target the UAT environment.		The examples you'll find in the collection target the UAT environment.
Line 23:		Line 29:
	The examples have been divided in several subfolders, listed and described as follows.		The examples have been divided in several subfolders, listed and described as follows.

	=====REST=====		=====REST =====
	The folder contains the examples related to the REST API.		The folder contains the examples related to the REST API.

	======Content Negotiation======		====== Content Negotiation======
	The content negotiation capabilities, as described [[ShareDoc:Content Negotiation\|in this page]]. Note there are three sub-folders that illustrate the three different ways to negotiate / request a given format.		The content negotiation capabilities, as described [[ShareDoc:Content Negotiation\|in this page]]. Note there are three sub-folders that illustrate the three different ways to negotiate / request a given format.

Line 34:		Line 40:
	By means of the Provenance API, the requestor can list the provenances that contributed to a given entity.		By means of the Provenance API, the requestor can list the provenances that contributed to a given entity.

	======Core Entities (e.g. Opus, Work, Instance)======		======Core Entities (e.g. Opus, Work, Instance) ======
	There is a folder for each type of entity managed in ShareVDE. API calls have been divided by entity for simplifying and better organising them.		There is a folder for each type of entity managed in ShareVDE. API calls have been divided by entity for simplifying and better organising them.

ShareDoc:Auth

Massimiliano Branca — Fri, 03 Jul 2026 12:51:56 GMT

← Older revision		Revision as of 12:51, 3 July 2026
Line 40:		Line 40:
	\|Advanced editing capabilities that allow full capabilities on Share-VDE resources. Includes the Basic Editor role.		\|Advanced editing capabilities that allow full capabilities on Share-VDE resources. Includes the Basic Editor role.
	\|}		\|}
	===~~Distinzione tra~~ scope ~~OAuth2 e ruoli~~===
	~~Non confondere lo~~ '''scope ~~OAuth2~~''' ~~con i~~ '''~~ruoli~~''':		===OAuth2 scope vs. roles===
	*~~Lo scope~~ <code>svde-resource-read</code> ~~è ciò che appare nel~~ token (~~campo~~ "scope" ~~della~~		Do not confuse the '''OAuth2 scope''' with '''roles''':
	~~risposta di autenticazione~~). ~~Garantisce l'accesso autenticato alle API~~.*~~Il ruolo~~ <code>svde-editor-base</code> ~~è un~~ '''~~ruolo~~ client ~~Keycloak~~''' (~~non uno~~ scope ~~OAuth2~~).		*The <code>svde-resource-read</code> scope is what appears in the token (the "scope" field of the
	~~Nella pratica~~, un token ~~con scope~~ <code>svde-resource-read</code> ~~ma senza ruolo~~ editor		authentication response). It grants authenticated access to the APIs.
	~~accede a tutte le API di lettura~~ '''~~eccetto~~''' ~~le ricerche~~ root <code>/works</code>,		*The <code>svde-editor-base</code> role is a '''Keycloak client role''' (not an OAuth2 scope).
	<code>/instances</code>, <code>/items</code>, <code>/dates</code> (~~che richiedono~~		In practice, a token with the <code>svde-resource-read</code> scope but no editor role can access all read APIs '''except''' the root searches <code>/works</code>, <code>/instances</code>,<code>/items</code> and <code>/dates</code> (which require <code>svde-editor-base</code>).
	<code>svde-editor-base</code>).		A read-only integration does not need any editor role.
	~~Per un'integrazione di sola lettura non serve alcun ruolo~~ editor.
	==<span style="color: #000000">API operations</span>==		==<span style="color: #000000">API operations</span>==

	===Obtain a new authentication token===		===Obtain a new authentication token ===
	The first request a client must make to authenticate with ShareVDE is the /token request.		The first request a client must make to authenticate with ShareVDE is the /token request.

Line 88:		Line 88:
	!Value (User auth)		!Value (User auth)
	\|-		\|-
	\|grant_type		\|grant_type
	\|The kind of grant operation that is going to be requested to the server		\|The kind of grant operation that is going to be requested to the server
	\|client_credentials		\| client_credentials
	\|password		\|password
	\|-		\|-
	\|username		\|username
	\|The user id to authenticate		\|The user id to authenticate
	\|Not applicable		\| Not applicable
	\|<Provided by the user>		\|<Provided by the user>
	\|-		\|-
Line 138:		Line 138:
	Regardless of the client or user authentication scenario, the successful authentication response has the same structure. Let’s analyze its contents:		Regardless of the client or user authentication scenario, the successful authentication response has the same structure. Let’s analyze its contents:

	*<code>access_token</code>: the token to be used to sign subsequent business REST requests (see the example later in this document). It is digitally signed by the Share-VDE realm.		*<code>access_token</code>: the token to be used to sign subsequent business REST requests (see the example later in this document). It is digitally signed by the Share-VDE realm.

	*<code>expires_in</code>: the token’s TTL (in seconds). After this number of seconds has passed since token emission, the token won’t be valid anymore, unless a refresh request is issued by the client.		*<code>expires_in</code>: the token’s TTL (in seconds). After this number of seconds has passed since token emission, the token won’t be valid anymore, unless a refresh request is issued by the client.
Line 149:		Line 149:
	*<code>scope</code>: a space-separated list of strings, showing the scopes represented by the access_token.		*<code>scope</code>: a space-separated list of strings, showing the scopes represented by the access_token.

	===Refresh an authentication token===		=== Refresh an authentication token===
	Via the <code>/token</code> request it is possible to request a new access token maintaining the same <code>session_status</code>.		Via the <code>/token</code> request it is possible to request a new access token maintaining the same <code>session_status</code>.

Line 182:		Line 182:
	!Value (user auth)		!Value (user auth)
	\|-		\|-
	\|grant_type		\|grant_type
	\|The kind of grant operation that is going to be requested to the server		\|The kind of grant operation that is going to be requested to the server
	\|refresh_token		\| refresh_token
	\|refresh_token		\|refresh_token
	\|-		\|-
	\|username		\|username
	\|The user id to authenticate		\|The user id to authenticate
	\|Not applicable		\| Not applicable
	\|<Provided by the user>		\|<Provided by the user>
	\|-		\|-
Line 197:		Line 197:
	\|<Provided by the user>		\|<Provided by the user>
	\|-		\|-
	\|client_id		\|client_id
	\|The client id used in the Authorization header		\| The client id used in the Authorization header
	\|<client_id>		\|<client_id>
	\|<client_id>		\|<client_id>
Line 205:		Line 205:
	\|The client secret used in the Authorization header		\|The client secret used in the Authorization header
	\|<client secret>		\|<client secret>
	\|<client secret>		\| <client secret>
	\|-		\|-
	\|refresh_token		\|refresh_token
	\|The refresh_token value received with the previous “new token” or “refresh token” response		\|The refresh_token value received with the previous “new token” or “refresh token” response
	\|<taken from the previous request>		\|<taken from the previous request>
	\|<taken from the previous request>		\|<taken from the previous request>
	\|}		\|}

Line 266:		Line 266:
	\|-		\|-
	\|401		\|401
	\|Unauthorized. The authentication is possible but has failed or has not been provided yet.		\|Unauthorized. The authentication is possible but has failed or has not been provided yet.
	\|-		\|-
	\|403		\|403
	\|Forbidden. The resource is available, but the authorization level is not sufficient in order to access it.		\|Forbidden. The resource is available, but the authorization level is not sufficient in order to access it.
	\|}		\|}

ShareDoc:API documentation

Massimiliano Branca — Fri, 03 Jul 2026 12:50:53 GMT

@@ Line 1,055: / Line 1,055: @@
 **in the [[ShareVDEmembers:APIdoc/RESTFul API/Search API#Stats|/stats]] component, for retrieving '''counts by provenance'''
 **in contexts (see for example the NATBIB tenant) where there '''are no items''' in the knowledge base. In such a context the "library" attribute it is not available because as said above, it is derived from items.
 ====[[ShareDoc:RESTFul API|REST]] Examples====

ShareDoc:GraphQL API

Massimiliano Branca — Fri, 03 Jul 2026 12:48:46 GMT

Show changes

ShareDoc:RESTFul API

Massimiliano Branca — Fri, 03 Jul 2026 12:44:43 GMT

← Older revision		Revision as of 12:44, 3 July 2026
Line 45:		Line 45:
	}		}
	</syntaxhighlight>		</syntaxhighlight>


			This navigation is also the intended way to reach works, instances and items with a read-only token: the
			root searches<code>/works</code>, <code>/instances</code>, <code>/items</code> and <code>/dates</code>
			require the <code>svde-editor-base</code> role, whereas hierarchical navigation (e.g.
			<code>/opuses/{id}/works</code> → <code>/works/{id}/instances</code> → ...) is accessible with the
			<code>svde-resource-read</code> scope alone.

	==Response Shape==		==Response Shape==
	A response can refers to three types of entities:		A response can refers to three types of entities:

	*a '''single''' '''resource'''		* a '''single''' '''resource'''
	*a '''collection''' of resources		*a '''collection''' of resources
	*a '''paged collection''' of resources		* a '''paged collection''' of resources

	Within the second and third response, each resource is represented using the first point.		Within the second and third response, each resource is represented using the first point.

	===Match Mode===		===Match Mode===
	The following endpoints		The following endpoints

	*/resources		*/resources
	*/agents		*/agents
	*/opuses		* /opuses

	return a paged collection with an additional '''meta''' section that informs the caller about the query match logic that has been executed. Here's an example: <syntaxhighlight lang="json">		return a paged collection with an additional '''meta''' section that informs the caller about the query match logic that has been executed. Here's an example: <syntaxhighlight lang="json">
Line 86:		Line 93:
	The explanation is typically requested on a given search result, after a query execution. Here's an example flow:		The explanation is typically requested on a given search result, after a query execution. Here's an example flow:

	#Simple search using one or more terms (e.g. history republic 1972)		# Simple search using one or more terms (e.g. history republic 1972)
	#Query response including entities E1, E2, E3		#Query response including entities E1, E2, E3
	#(on demand) Explain for E1		#(on demand) Explain for E1
Line 109:		Line 116:
	Returns a single resource which consists of the requested explanation (i.e. highlighting snippets of the matching terms).		Returns a single resource which consists of the requested explanation (i.e. highlighting snippets of the matching terms).

	Each snippets refers to a specific attribute which follows these rules		Each snippets refers to a specific attribute which follows these rules

	*it contains the matching terms highlighted (e.g. surrounded by a "bold" html marker		*it contains the matching terms highlighted (e.g. surrounded by a "bold" html marker
	<syntaxhighlight lang="json">		<syntaxhighlight lang="json">
	/~~organisations~~/101/explanation?terms=american%20library		/organizations/101/explanation?terms=american%20library

	{		{
Line 152:		Line 159:

	*in case the language is '''"und" (undefined) it is not included''' in the value		*in case the language is '''"und" (undefined) it is not included''' in the value
	*'''it can be nested''', when the attribute is indirect (i.e. it doesn't belong directly to the requested entity). Each part of the attribute name can represent		* '''it can be nested''', when the attribute is indirect (i.e. it doesn't belong directly to the requested entity). Each part of the attribute name can represent
	**the '''attribute name''' itself (e.g. nameAlternative, label, altLabel)		**the '''attribute name''' itself (e.g. nameAlternative, label, altLabel)
	**the '''referred nested entity''' (e.g. instance, work)		** the '''referred nested entity''' (e.g. instance, work)
	**the '''relator code''' (e.g. aut = author, ill = illustrator, pbl = publisher)		**the '''relator code''' (e.g. aut = author, ill = illustrator, pbl = publisher)
	**the '''subject type code''' (e.g. top = topical subject, nameSubject = name subject)		**the '''subject type code''' (e.g. top = topical subject, nameSubject = name subject)
Line 278:		Line 285:
	[https://uat3-base-svde.atcult.it/opuses/411/explanation?terms=Georgia%20Press Example #12: Opus explanation: publisher (instance contributor) data]		[https://uat3-base-svde.atcult.it/opuses/411/explanation?terms=Georgia%20Press Example #12: Opus explanation: publisher (instance contributor) data]
	===Resource===		===Resource===
	A resource returned in a response is represented using two sets of attributes:		A resource returned in a response is represented using two sets of attributes:

	*'''direct attributes''' whose values are literals (e.g. strings, numbers)		*'''direct attributes''' whose values are literals (e.g. strings, numbers)
Line 293:		Line 300:
	"_links": {		"_links": {
	...		...
	</syntaxhighlight>note the links includes also references to the resource itself. Those references, in a special section called "self" could be		</syntaxhighlight>note the links includes also references to the resource itself. Those references, in a special section called "self" could be

	*'''Share-VDE''' URIs		* '''Share-VDE''' URIs
	*'''External URIs''': in this a "type" attribute indicates the source:		* '''External URIs''': in this a "type" attribute indicates the source:
	<syntaxhighlight lang="json">		<syntaxhighlight lang="json">
	"_links": {		"_links": {
Line 320:		Line 327:
	],		],
	</syntaxhighlight>		</syntaxhighlight>
	===Collection===		=== Collection ===
	A list of resources with a predefined and relatively small size. The only example we have at the moment is the collection of [https://uat3-base-svde.atcult.it/people/201/occupations.json occupations] associated with a given person:<syntaxhighlight lang="json">		A list of resources with a predefined and relatively small size. The only example we have at the moment is the collection of [https://uat3-base-svde.atcult.it/people/201/occupations.json occupations] associated with a given person:<syntaxhighlight lang="json">
	{		{
Line 361:		Line 368:
	}		}
	}		}
	</syntaxhighlight>As you can see, the collection is a simple list of resources. In addition, it provides two top level links:		</syntaxhighlight>As you can see, the collection is a simple list of resources. In addition, it provides two top level links:

	*a link to the collection itself (self)		*a link to the collection itself (self)
Line 373:		Line 380:
	*'''the search can be a fulltext search''' (e.g. give me all agents whose name is andrea) or a '''boolean''' (e.g. give me all opuses where the agent XYZ is the author)		*'''the search can be a fulltext search''' (e.g. give me all agents whose name is andrea) or a '''boolean''' (e.g. give me all opuses where the agent XYZ is the author)
	*search results '''can be''' '''refined''' by using '''one or more filters''' (e.g. filter by a specific publication year)		*search results '''can be''' '''refined''' by using '''one or more filters''' (e.g. filter by a specific publication year)
	*search results '''can be sorted''' by a given criteria. In case of fulltext search the default sort criterion is '''by relevance'''		* search results '''can be sorted''' by a given criteria. In case of fulltext search the default sort criterion is '''by relevance'''

	The response contains '''3 sections''':		The response contains '''3 sections''':

	*the page including the resources. Each resource is represented according to its type following what we described [[ShareVDEmembers:Apidoc/RESTFul API#Resource\|previously]]		*the page including the resources. Each resource is represented according to its type following what we described [[ShareVDEmembers:Apidoc/RESTFul API#Resource\|previously]]
	*[[ShareVDEmembers:APIdoc#Pagination\|pagination]] metadata: three attributes ('''totalMatches''', '''pageSize''' and '''startOffset''')		* [[ShareVDEmembers:APIdoc#Pagination\|pagination]] metadata: three attributes ('''totalMatches''', '''pageSize''' and '''startOffset''')
	*facets: aggregations over the entity attributes. Facets depend on the type of the returned entities		*facets: aggregations over the entity attributes. Facets depend on the type of the returned entities
	<syntaxhighlight lang="json">		<syntaxhighlight lang="json">
Line 495:		Line 502:

	===[[ShareDoc:Search API\|Search API]]===		===[[ShareDoc:Search API\|Search API]]===
	This category includes all endpoints that are part of the '''Share-VDE Search API''': ~~they~~ require ~~a caller having a '''minimal role''' level ('''~~svde-~~reader''')~~.		This category includes all endpoints that are part of the '''Share-VDE Search API''': requires a valid token with the <code>svde-resource-read</code> scope. Most
			endpoints are accessible with this scope alone. The exceptions are the root searches <code>/works</code>,
			<code>/instances</code>, <code>/items</code> and <code>/dates</code>, which require the
			<code>svde-editor-base</code> role.

	[[ShareDoc:Search API\|The available endpoints are detailed in this page]].<br />		[[ShareDoc:Search API\|The available endpoints are detailed in this page]].<br />
	__FORCETOC__		__FORCETOC__

ShareDoc:Search API

Massimiliano Branca — Fri, 03 Jul 2026 12:39:40 GMT

Show changes

ShareDoc:Auth

Massimiliano Branca — Fri, 03 Jul 2026 07:47:25 GMT

← Older revision		Revision as of 07:47, 3 July 2026
Line 40:		Line 40:
	\|Advanced editing capabilities that allow full capabilities on Share-VDE resources. Includes the Basic Editor role.		\|Advanced editing capabilities that allow full capabilities on Share-VDE resources. Includes the Basic Editor role.
	\|}		\|}
			===Distinzione tra scope OAuth2 e ruoli===
			Non confondere lo '''scope OAuth2''' con i '''ruoli''':
			*Lo scope <code>svde-resource-read</code> è ciò che appare nel token (campo "scope" della
			risposta di autenticazione). Garantisce l'accesso autenticato alle API.*Il ruolo <code>svde-editor-base</code> è un '''ruolo client Keycloak''' (non uno scope OAuth2).
			Nella pratica, un token con scope <code>svde-resource-read</code> ma senza ruolo editor
			accede a tutte le API di lettura '''eccetto''' le ricerche root <code>/works</code>,
			<code>/instances</code>, <code>/items</code>, <code>/dates</code> (che richiedono
			<code>svde-editor-base</code>).
			Per un'integrazione di sola lettura non serve alcun ruolo editor.
	==<span style="color: #000000">API operations</span>==		==<span style="color: #000000">API operations</span>==

ShareFamily:Resources

Anna — Mon, 29 Jun 2026 16:40:53 GMT

← Older revision		Revision as of 16:40, 29 June 2026
Line 92:		Line 92:

	=== Year 2026 ===		=== Year 2026 ===
			''[https://wiki.share-vde.org/w/images/b/b7/Full_presentations_Share_Family_Workshop_ALA_2026-Jun-29.pdf Share Family Workshop]'', at ALA Annual, June 30 2025, by Jill Morris, Sebastian Hammer, Tiziana Possemato, Anna Lionetti; [https://youtu.be/EcZwWQoRJKw recording available].

	[https://wiki.share-vde.org/w/images/7/70/LC_BF_Forum_January-2026_static_version.pptx.pdf ''BIBFRAME in Practice: Powering a Collaborative Share Family Community with JCricket''], at LC BIBFRAME Update Forum, 9 February 2026, by Tiziana Possemato and Anna Lionetti; [https://www.loc.gov/bibframe/news/bibframe-update-feb2026.html materials and recording available].		[https://wiki.share-vde.org/w/images/7/70/LC_BF_Forum_January-2026_static_version.pptx.pdf ''BIBFRAME in Practice: Powering a Collaborative Share Family Community with JCricket''], at LC BIBFRAME Update Forum, 9 February 2026, by Tiziana Possemato and Anna Lionetti; [https://www.loc.gov/bibframe/news/bibframe-update-feb2026.html materials and recording available].

ShareFamily:Resources

Serena Cericola — Mon, 29 Jun 2026 08:39:39 GMT

← Older revision		Revision as of 08:39, 29 June 2026
Line 51:		Line 51:
	''Share-VDE and Beyond: Cooperation and Innovation to Bring Linked Open Data into Practice'', by Jim Hahn, Sebastian Hammer, Tiziana Possemato, Nina Servizzi, in «Charleston Conference Proceedings, 2023», 309-333 (2024) https://doi.org/10.3998/mpub.14509768.		''Share-VDE and Beyond: Cooperation and Innovation to Bring Linked Open Data into Practice'', by Jim Hahn, Sebastian Hammer, Tiziana Possemato, Nina Servizzi, in «Charleston Conference Proceedings, 2023», 309-333 (2024) https://doi.org/10.3998/mpub.14509768.

	''Un esempio di entity modeling: l’Opus in Share-VDE, Proprietà delle entità svde:Opus, svde:Work'' e ''bf:Hub'', ''L’ontologia Share-VDE: un’estensione di BIBFRAME per la discovery dei linked data'', ''L'ontologia di Share-VDE come estensione di BIBFRAME'', by Tiziana Possemato, in «Entity modeling: la terza generazione della catalogazione», 112-138, 281-302 (2024); free online access https://doi.org/10.36253/979-12-215-0393-7.		''Un esempio di entity modeling: l’Opus in Share-VDE, Proprietà delle entità svde:Opus, svde:Work'' e ''bf:Hub'', ''L’ontologia Share-VDE: un’estensione di BIBFRAME per la discovery dei linked data'', ''L'ontologia di Share-VDE come estensione di BIBFRAME'', by Tiziana Possemato, in «Entity modeling: la terza generazione della catalogazione», 112-138, 281-302 (2024); free online access https://doi.org/10.36253/979-12-215-0393-7. The English translation of this book is available at https://www.facetpublishing.co.uk/page/detail/entity-modelling/?k=9781783307272.

	''A Comparative Evaluation of the Share-VDE Search System'', by Jim Hahn, Kayt Ahnberg, Liliana Giusti Serra (2024); free online access https://repository.upenn.edu/entities/publication/650624f3-9d82-43d8-b268-04dfe33c636b, DOI https://doi.org/10.1080/01639374.2024.2372680.		''A Comparative Evaluation of the Share-VDE Search System'', by Jim Hahn, Kayt Ahnberg, Liliana Giusti Serra (2024); free online access https://repository.upenn.edu/entities/publication/650624f3-9d82-43d8-b268-04dfe33c636b, DOI https://doi.org/10.1080/01639374.2024.2372680.