Wikidata:Property proposal/SCTA ID

SCTA ID edit

Originally proposed at Wikidata:Property proposal/Generic

   Not done
Descriptionlinked data identifiers maintained by the Scholastic Commentaries and Texts Archive (https://scta.info/)
RepresentsShould be included under "Identifiers"
Data typeURL
DomainWhile the SCTA has IDs for thousands texts, text parts, and codices, the primary use case in connecting to wiki data would likely be people, either authors or people mentioned within scholastic texts. So the usual domain would be "People" (see examples 1-4), but could also extend to "Works" and "Manuscripts/Codices" which contain said "Works" if this resource type exist in wikidata. (See example 5 for an example of connection to a top level work, but note that for most of the works catalogue by the SCTA there are no wikidata entries -->
Example 1https://www.wikidata.org/wiki/Q9438 -> Aquinas
Example 2https://www.wikidata.org/wiki/Q7176408 -> peter-plaoul
Example 3https://www.wikidata.org/wiki/Q454349 -> per-jjska2
Example 4https://www.wikidata.org/wiki/Q543373 -> per-x84nST
Example 5https://www.wikidata.org/wiki/Q653871 -> TAca84
Planned useBecause the SCTA makes full text transcriptions of scholastic works available, we've discussed use cases with various libraries or library portals (e.g. https://biblissima.fr/) where a connection between a library identifer and the SCTA identifier could be brokered (discovered) through wiki-data. From there a library (or any project) could traverse the SCTA data structure to find known works by a scholastic author, find known manuscripts/codices, and locate transcriptions of a given work. They could then present this information to their end user without having to send them away from their home portal.
Number of IDs in sourceWe currently have 469 person ids and roughly 300 top-level text/work ids. (with hundreds of thousands of ids for textual parts that will likely be "out of scope" for wikidata. The advantage of connecting at the Person or topLevel Work through wikidata is that users can move through wikidata to the SCTA to discover all of the granular text part resources that the SCTA catalogues.
Expected completenessCompleteness seems feasible at the person or author level. For every scta author that has an wikidata entry, there no reason there couldn't be a complete mapping. For SCTA people entries without a wikidata entry, such an entry would need to be made. But this is another contribution the SCTA could make to wikidata. Once all known connections are mapped, we could produced a list of all known scholastic people (authors or persons mentioned) without a wikidata entry and then batch generate new wikidata entries from the known SCTA information.
Formatter URLhttp://scta.info/resource/$1

Motivation edit

Because the SCTA makes full text transcriptions of scholastic works available, we've discussed use cases with various libraries or library portals (e.g. https://biblissima.fr/) where a connection between a library identifer and the SCTA identifier could be brokered (discovered) through wiki-data. From there a library (or any project) could traverse the SCTA data structure to find known works by a scholastic author, find known manuscripts/codices, and locate transcriptions of a given work. They could then present this information to their end user without having to send them away from their home portal.  – The preceding unsigned comment was added by Jeffreycwitt (talk • contribs) at 13:45, August 22, 2021‎ (UTC).

Discussion edit