Property talk:P6329
Documentation
identifier for entities (people and organizations) in the federated linked data platform Share Virtual Discovery Environment
List of violations of this constraint: Database reports/Constraint violations/P6329#Type Q5, Q43229, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P6329#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P6329#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P6329#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P6329#Entity types
List of violations of this constraint: Database reports/Constraint violations/P6329#Scope, SPARQL
Replacement with version 2.0?
edit
Apparently Share Virtual Discovery Environment and share-vde.org
will someday potentially be retired and replaced by Share Virtual Discovery Environment 2.0 and svde.org
. The 1.0 homepage currently reads:
Share-VDE gets even better!
To access the new Entity Discovery Portal and get information on how to connect with the Share-VDE 2.0 Linked Data Management System go to https://svde.org
This portal will be active in parallel to Share-VDE 2.0 for a while, but if you want to discover the new, updated Share-VDE https://svde.org is the place to go.
— share-vde.org [emphasis added]
As an example, Michael Crichton is available on 1.0 at https://www.share-vde.org/sharevde/searchNames?n_cluster_id=656533 and on 2.0 at https://svde.org/agents/201645700505668 (a redirect to https://www.svde.org/michael-crichton-a201645700505668/original-works-by) so it looks like the 2.0 ids are different. Chchowmein (talk) 22:46, 23 April 2022 (UTC)
- @Chchowmein: Thanks for the news! In my opinion, since this property has just a few uses (less than 1000), I would support deleting all the existing IDs and using this property for the new ones. --Epìdosis 23:02, 23 April 2022 (UTC)
- @Epìdosis That sounds like a good solution. Reading more on their pages just now, one consideration might be timing: despite the message on the homepage they may be still migrating from 1.0 to 2.0 themselves. As of September, they announced that information from 2 member libraries was transferred to 2.0. but there are 13 to 26 libraries involved so their progress is unclear. However a post confirms the impending sun-setting: "The previous version at https://share-vde.org/ will be active in parallel to Share-VDE 2.0 until the migration of libraries’ data on the new system will be completed."
- Apparently there is a common API is powering both Portal 1.0 and Portal 2.0 so hopefully there will be an easy way to match the IDs. In January, their most recent post says that "we look forward to start working on the inclusion of Wikidata and ISNI data". Judging by Crichton, the entities on the both the 1.0 portal and the 2.0 portal seem to already be linked to Wikidata, I presume using VIAF. For now I have updated the label on this property to specify it is (currently) 1.0 I suppose until we can locate the resource/access that correlates the IDs. Chchowmein (talk) 00:00, 24 April 2022 (UTC)
- @Epìdosis Hi, the IDs of SVDE 2.0 are not stable. The portal is in a beta version, because some tests are still in progress: usually, each upload of data libraries is following by a trial period aimed at individuate problems and bugs. After the upload of all libraries data, there will be new releases and the CKB will be re-clusterized, so URIs will certainly change. Alessandra.Moi (talk) 20:38, 27 April 2022 (UTC)
- Will the unique ID's change or just the URI? I can already see different URI's for "opuses" and "agents" given they are happy to change id's formats perhaps we could use more independent ID's to access it such as VIAF Back ache (talk) 14:36, 23 August 2022 (UTC)
- @Epìdosis Hi, the IDs of SVDE 2.0 are not stable. The portal is in a beta version, because some tests are still in progress: usually, each upload of data libraries is following by a trial period aimed at individuate problems and bugs. After the upload of all libraries data, there will be new releases and the CKB will be re-clusterized, so URIs will certainly change. Alessandra.Moi (talk) 20:38, 27 April 2022 (UTC)