Property talk:P3827

Latest comment: 1 year ago by Bovlb in topic Thread on Project Chat

Documentation

JSTOR topic ID (archived)
identifier for a topic at JSTOR
[create Create a translatable help page (preferably in English) for this property to be included here]
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3827#Unique value, SPARQL (every item), SPARQL (by value)
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: social mobility (Q194417), drought tolerance (Q12142810)
List of violations of this constraint: Database reports/Constraint violations/P3827#Single value, SPARQL
Format “[^\s/?°`#;$]+: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P3827#Format, hourly updated report, SPARQL
Conflicts with “instance of (P31): Wikimedia list article (Q13406463): this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3827#Conflicts with P31, search, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3827#Entity types
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3827#Scope, SPARQL

Single value?

edit

I deprecated this constraint because as I see this property connects to some type of "search keywords" at the site so they can possibly be of many variants. --Infovarius (talk) 21:47, 20 July 2020 (UTC)Reply

I restored it to normal rank, as there was no qualifier added for the deprecation reason. But more importantly, this property acts a Wikidata property for authority control, with reciprocal use of Wikidata (Q24075706) with JSTOR (Q1420342). Incorrect and multiple JSTOR topics added to Wikidata items have been flooding the JSTOR site with incorrect data. JSTOR users can negatively flag the information. If JSTOR receives a significant amount of negative feedback through the flagging, or by other means, it likely would no longer have the incentive to share, or at the very least, utilize an unreliable data source.

One example, for multiple usage on a single Wikidata item: canning (Q843389) is linked to (1) Topic: Canned Food, while there is an existing item for canned food (Q18396746). (2) linked to Topic: Canneries, while cannery (Q1922209) exists. Additionally connected to (3) Topic: Canned Fruit and (4) Topic: Canning Industry; a one-to-four correspondence. — Dcflyer (talk) 10:03, 6 August 2020 (UTC)Reply

edit

I opened a topic about this on Project chat how the JSTOR links are broken/invalid Datariumrex (talk) 08:56, 2 September 2020 (UTC)Reply

I've contacted the JSTOR through the chat system

edit

The chat was opened moments ago from https://support.jstor.org/hc/en-us

This is how the conversation went: Datariumrex(Me):

That is not an email I provide but I semantically try to communicate to you
that you can contact me on wikidata.org on my userpage.
There is a correlation as I have brought the subject up
to the wikidata.org community that links are broken to your site.
Hi. I'm an editor for wikidata.org. We have a system to interact with your site
but due to a change in how your site works all JSTOR links on wikidata are now broken.
Specifically the formatter URL we use in relation to your website "https://www.jstor.org/topic/$1"

Scott(JSTOR support):

Hi! We've deactivated our topics functionality temporarily
That's why this link is no longer operating as it did before

Me:

Ok, then I can add that to the talk page. Thank you for an answer.
Can I quote you with your name "Scott"?

Scott:

Sure.

Me:

Thank you for the help. I have no other issue. Thanks again

Scott:

We're looking to reactivate our topics functionality sometime near the end of the month; 
I would expect that then these links should function for you as they did before
If you have any other questions, just let me know and I would be happy to help.

Me:

Thank you. I have no other questions.

That's how it concluded. I tried to quote it as is and not modifying the original, not even modifying punctuation marks or a lack there of. Did this help or was it too much text? If you know how to condense it feel free to. If you have any other comment about how I worded my communication with JSTOR support let me know as that can help me improve my future communication. Datariumrex (talk) 13:04, 18 September 2020 (UTC)Reply

Thread on Project Chat

edit

https://www.wikidata.org/w/index.php?title=Wikidata%3AProject_chat&oldid=1920801662#Delete_Property_JSTOR_topic_ID_(P3827)_-_JSTOR_Topic_ID Bovlb (talk) 17:56, 21 June 2023 (UTC)Reply

Return to "P3827" page.