Anna at 16:55, 2 February 2026

2026-02-02T16:55:32Z

Anna at 16:43, 2 February 2026

2026-02-02T16:43:40Z

Anna at 16:40, 2 February 2026

2026-02-02T16:40:40Z

Show changes

Anna at 16:23, 2 February 2026

2026-02-02T16:23:15Z

Show changes

Anna at 16:12, 2 February 2026

2026-02-02T16:12:07Z

Show changes

Anna at 15:01, 27 January 2026

2026-01-27T15:01:17Z

Show changes

Anna: Created page with "{{DISPLAYTITLE:Share Family Bulletin - n. 10 April 2025}} You can download a printable version at https://bit.ly/SFBulletin_n10_Apr2025 Citation: Share Family Team, ''Share Family Bulletin'' ''10'' (April 2025), https://bit.ly/SFBulletin_n10_Apr2025"

2026-01-27T14:59:56Z

Created page with "{{DISPLAYTITLE:Share Family Bulletin - n. 10 April 2025}} You can download a printable version at https://bit.ly/SFBulletin_n10_Apr2025 Citation: Share Family Team, ''Share Family Bulletin'' ''10'' (April 2025), https://bit.ly/SFBulletin_n10_Apr2025"

New page

{{DISPLAYTITLE:Share Family Bulletin - n. 10 April 2025}}

You can download a printable version at https://bit.ly/SFBulletin_n10_Apr2025

Citation: Share Family Team, ''Share Family Bulletin'' ''10'' (April 2025), https://bit.ly/SFBulletin_n10_Apr2025

← Older revision		Revision as of 16:43, 2 February 2026
Line 30:		Line 30:

	* allowing a single conversion pipeline that does not use MARC structure as an intermediate BIBFRAME conversion step;		* allowing a single conversion pipeline that does not use MARC structure as an intermediate BIBFRAME conversion step;
	* prepare the data structure for the new NoSQL database that will be implemented (see also the ~~[https://docs.google.com/document/d/1pk3iVEw_Hlww6dpyrW7rIUfnTQKax41lXae2q5V9uRM/edit?tab=t.0#heading=h.cwlyr8fvnbmv~~ Architecture and infrastructure section] below).		* prepare the data structure for the new NoSQL database that will be implemented ('''see also the Architecture and infrastructure section''' below).

	As part of the granularization work, attributes that were previously managed as literals are now controlled vocabularies sets; therefore, they have been clustered and assigned a URI.		As part of the granularization work, attributes that were previously managed as literals are now controlled vocabularies sets; therefore, they have been clustered and assigned a URI.
Line 37:		Line 37:
	Share Family members have been testing [[ShareDoc:PublicDocumentation/LODPlatform/EntityEditor\|JCricket]] throughout 2025 and raised input for improvement, while the Share Family team has been continuing the work on new features to enable granular and effective cataloguing and progressively make JCricket a production-ready tool.		Share Family members have been testing [[ShareDoc:PublicDocumentation/LODPlatform/EntityEditor\|JCricket]] throughout 2025 and raised input for improvement, while the Share Family team has been continuing the work on new features to enable granular and effective cataloguing and progressively make JCricket a production-ready tool.

	Among these features, it’s worth mentioning the advancement in the integration with third parties’ systems (see ~~[https://docs.google.com/document/d/1pk3iVEw_Hlww6dpyrW7rIUfnTQKax41lXae2q5V9uRM/edit?tab=t.0#heading=h.43igfzquu2gn~~ Third parties integration] section), the creation of the Provision Activity metadata block and the review of the Provenance-based function.		Among these features, it’s worth mentioning the advancement in the integration with third parties’ systems ('''see the Third parties integration section''' below), the creation of the Provision Activity metadata block and the review of the Provenance-based function.

	'''Provision Activity''' is a set of attributes of the Instance entity that represent an event or action describing:		'''Provision Activity''' is a set of attributes of the Instance entity that represent an event or action describing:
Line 46:		Line 46:

	This new metadata block serves not only the enrichment of the information available for an entity, but also the curation of publisher data according to RDA guidelines (e.g. the ability to record the Publication statement). Also, the Provision Activity is in fact a multi-entity metadata block, because it includes information that is described as individual entities in their turn. So, we needed JCricket to handle this complex data structure that will also serve other use cases: this multi-entity metadata block approach will be used for the management of Subject entities in JCricket.		This new metadata block serves not only the enrichment of the information available for an entity, but also the curation of publisher data according to RDA guidelines (e.g. the ability to record the Publication statement). Also, the Provision Activity is in fact a multi-entity metadata block, because it includes information that is described as individual entities in their turn. So, we needed JCricket to handle this complex data structure that will also serve other use cases: this multi-entity metadata block approach will be used for the management of Subject entities in JCricket.
	[[File:Provision Activity.png\|none\|thumb\|594x594px\|https://wiki.share-vde.org/w/images/6/66/Provision_Activity.png]]		[[File:Provision Activity.png\|none\|thumb\|594x594px\|https://wiki.share-vde.org/w/images/6/66/Provision_Activity.png]]

	The LOD Platform system is '''Provenance-based''', meaning that the relationship between the entity and the source record that contributed to its creation is always retained through the Provenance, in order to maintain the relationship with the data that generated an entity over time and allow to manage the entity both in automated update processes and in manual processes (via JCricket entity editor). '''See also [[ShareDoc:PublicDocumentation/LODPlatform/EntityEditor#Provenance%20and%20Prism\|the wiki section on the Provenance]]'''.		The LOD Platform system is '''Provenance-based''', meaning that the relationship between the entity and the source record that contributed to its creation is always retained through the Provenance, in order to maintain the relationship with the data that generated an entity over time and allow to manage the entity both in automated update processes and in manual processes (via JCricket entity editor). '''See also [[ShareDoc:PublicDocumentation/LODPlatform/EntityEditor#Provenance%20and%20Prism\|the wiki section on the Provenance]]'''.
Line 82:		Line 82:
	[[File:Cooperative cat. in FOLIO.png\|none\|thumb\|449x449px\|https://wiki.share-vde.org/w/images/6/68/Cooperative_cat._in_FOLIO.png]]		[[File:Cooperative cat. in FOLIO.png\|none\|thumb\|449x449px\|https://wiki.share-vde.org/w/images/6/68/Cooperative_cat._in_FOLIO.png]]
	[[File:Cooperative cat. in Alma.png\|none\|thumb\|447x447px\|https://wiki.share-vde.org/w/images/4/4b/Cooperative_cat._in_Alma.png]]		[[File:Cooperative cat. in Alma.png\|none\|thumb\|447x447px\|https://wiki.share-vde.org/w/images/4/4b/Cooperative_cat._in_Alma.png]]
			The integration with external ILS / LSP contributes to shaping a cooperative cataloguing environment, an integrated workflow where local and central systems are fully interoperable: data entered locally is reflected centrally, and conversely, central data is discoverable and reusable locally. The focus is on bidirectional synchronization; cataloging gains added value by keeping local and central environments aligned. This model enables full interoperability between local and central systems, ensuring that data flows in both directions. This new cooperative cataloging scenario is built on strong interoperability between systems, allowing libraries the freedom to design their own workflows — whether starting from the central hub or from the local environment — depending on their specific cataloging needs at any given time.

	The integration with external ILS / LSP contributes to shaping a cooperative cataloguing environment, an integrated workflow where local and central systems are fully interoperable: data entered locally is reflected centrally, and conversely, central data is discoverable and reusable locally. The focus is on bidirectional synchronization; cataloging gains added value by keeping local and central environments aligned. This model enables full interoperability between local and central systems, ensuring that data flows in both directions. This new cooperative cataloging scenario is built on strong interoperability between systems, allowing libraries the freedom to design their own workflows — whether starting from the central hub or from the local environment — depending on their specific cataloging needs at any given time.		The integration with external ILS / LSP contributes to shaping a cooperative cataloguing environment, an integrated workflow where local and central systems are fully interoperable: data entered locally is reflected centrally, and conversely, central data is discoverable and reusable locally. The focus is on bidirectional synchronization; cataloging gains added value by keeping local and central environments aligned. This model enables full interoperability between local and central systems, ensuring that data flows in both directions. This new cooperative cataloging scenario is built on strong interoperability between systems, allowing libraries the freedom to design their own workflows — whether starting from the central hub or from the local environment — depending on their specific cataloging needs at any given time.
Line 126:		Line 127:
	* definition of the technical roles.		* definition of the technical roles.

	The [[ShareVDE:Members/Share-VDE working groups#Sapientia%20Entity%20Identification%20working%20group%20(SEI)\|'''SEI - Sapientia Entity Identification working group''']] continues to play a critical role in modeling the data structure and the [https://zenodo.org/doi/10.5281/zenodo.8332350 '''SVDE Ontology'''] underlying the LOD Platform system.		The [[ShareVDE:Members/Share-VDE working groups#Sapientia%20Entity%20Identification%20working%20group%20(SEI)\|'''SEI - Sapientia Entity Identification working group''']] continues to play a critical role in modeling the data structure and the [https://zenodo.org/doi/10.5281/zenodo.8332350 '''SVDE Ontology'''] underlying the LOD Platform system.

	[[File:SVDE ontology.png\|none\|thumb\|503x503px\|https://wiki.share-vde.org/w/images/a/ac/SVDE_ontology.png]]		[[File:SVDE ontology.png\|none\|thumb\|503x503px\|https://wiki.share-vde.org/w/images/a/ac/SVDE_ontology.png]]
			The group has been working and will continue to address:

	The group has been working and will continue to address:		The group has been working on and will continue to address:

	* modeling the Opus type properties;		* modeling the Opus type properties;
Line 138:		Line 140:

	The [[ShareVDE:Members/Share-VDE working groups#SVDE-AC%20User%20Experience.2FUser%20Interface%20working%20group%20.28UX-UI.29\|'''User Experience – User Interface Working Group''']] has worked jointly with the [[ShareVDE:Members/Share-VDE working groups#Share%20Family%20National%20Bibliographies%20working%20group%20.28Natbib.29\|National Bibliographies Working Group]] to restructure the Publication entity page of the Entity Discovery Portal, with the aim of presenting information in a more streamlined fashion, to offer data consumers and cataloguers among Share Family members a better user experience. This has entailed partial restructuring of back-end-to-front-end data flows and to the UI design (see the [https://docs.google.com/document/d/1pk3iVEw_Hlww6dpyrW7rIUfnTQKax41lXae2q5V9uRM/edit?tab=t.0#heading=h.nlpizdhi0cgd Front-end enhancements section] above).		The [[ShareVDE:Members/Share-VDE working groups#SVDE-AC%20User%20Experience.2FUser%20Interface%20working%20group%20.28UX-UI.29\|'''User Experience – User Interface Working Group''']] has worked jointly with the [[ShareVDE:Members/Share-VDE working groups#Share%20Family%20National%20Bibliographies%20working%20group%20.28Natbib.29\|National Bibliographies Working Group]] to restructure the Publication entity page of the Entity Discovery Portal, with the aim of presenting information in a more streamlined fashion, to offer data consumers and cataloguers among Share Family members a better user experience. This has entailed partial restructuring of back-end-to-front-end data flows and to the UI design (see the [https://docs.google.com/document/d/1pk3iVEw_Hlww6dpyrW7rIUfnTQKax41lXae2q5V9uRM/edit?tab=t.0#heading=h.nlpizdhi0cgd Front-end enhancements section] above).



Line 167:		Line 170:

	Moreover, participation in international working groups and networks is strategic to the Share Family community, and responds to its core principle of creating connections and increasing communication across initiatives and projects.		Moreover, participation in international working groups and networks is strategic to the Share Family community, and responds to its core principle of creating connections and increasing communication across initiatives and projects.

ShareFamily:NewsAndUpdates/April2025 - Revision history

Anna at 16:55, 2 February 2026

Anna at 16:43, 2 February 2026

Anna at 16:40, 2 February 2026

Anna at 16:23, 2 February 2026

Anna at 16:12, 2 February 2026

Anna at 15:01, 27 January 2026

Anna: Created page with "{{DISPLAYTITLE:Share Family Bulletin - n. 10 April 2025}} You can download a printable version at https://bit.ly/SFBulletin_n10_Apr2025 Citation: Share Family Team, ''Share Family Bulletin'' ''10'' (April 2025), https://bit.ly/SFBulletin_n10_Apr2025"