DOI unrecognised

Please can you have a look at this auto response from CrossRef and tell me if the basic doi for the Journal at www.murmurations.cloud is operational. None of the article dois work. I wondered if the journal one works. It is https://doi.org/10.28963

It brings up the following rather than jumping to the journal home page.

DOI Name Values

DOI: 10.28963
DOI Values for: 10.28963
Index Type Timestamp Data
100 HS_ADMIN 2017-09-28 19:27:55Z handle=0.NA/10; index=200; [delete hdl,read val,modify val,del val,add val,modify admin,del admin,add admin,list]
101 HS_ADMIN 2017-09-28 19:27:55Z handle=10.SERV/CROSSREF; index=200; [create hdl,read val,modify val,del val,add val,modify admin,list]
1 HS_SERV 2017-09-28 19:27:55Z 10.SERV/CROSSREF
2 EMAIL 2017-09-28 19:27:55Z support@crossref.org
3 DESC 2017-09-28 19:27:55Z Crossref Prefix 9/28/17
500 HS_NAMESPACE 2017-09-28 19:27:55Z <HS_NAMESPACE> <DOI.RA>10.SERV/CROSSREF</DOI.RA> 10.SERV/CROSSREF </HS_NAMESPACE>
400 HS_SIGNATURE 2018-03-01 20:08:22Z (https://doi.org/static/img/transparent.gif)

This is the landing page for your DOI prefix. It is not expected to redirect to your journal. A journal level DOI, if created, would be a specific DOI under this prefix, along with your article DOIs.

Okay. Thank you. So the doi for the journal is working. The dois for the papers are not. Any idea why?

Do you use the CrossRef plugin for registration, or some other means? If the CrossRef plugin, do you use automatic registration, manual registration within the plugin, or do you manually export and upload the XML file? If you use registration within the plugin, does the CrossRef plugin indicate that these DOIs have been registered with CrossRef?

In The CrossRef plugin in OJS 3.02, I get the following message:
{“status”:true,“content”:"\n
Please configure the DOI plugin to be able to manage and use DOIs in OJS:</div>\n\n

When I go to DOI PLUGIN SEETINGS, I see this:

We have four issues with doi format: https://doi.org/10.28963/2.2.1 - none of which have ever worked.

The metadata shows:
identifier

Feedback from the journal doi.org page:

DOI Name Values

DOI: 10.28963
DOI Values for: 10.28963
Index Type Timestamp Data
100 HS_ADMIN 2017-09-28 19:27:55Z handle=0.NA/10; index=200; [delete hdl,read val,modify val,del val,add val,modify admin,del admin,add admin,list]
101 HS_ADMIN 2017-09-28 19:27:55Z handle=10.SERV/CROSSREF; index=200; [create hdl,read val,modify val,del val,add val,modify admin,list]
1 HS_SERV 2017-09-28 19:27:55Z 10.SERV/CROSSREF
2 EMAIL 2017-09-28 19:27:55Z support@crossref.org
3 DESC 2017-09-28 19:27:55Z Crossref Prefix 9/28/17
500 HS_NAMESPACE 2017-09-28 19:27:55Z <HS_NAMESPACE> <DOI.RA>10.SERV/CROSSREF</DOI.RA> 10.SERV/CROSSREF </HS_NAMESPACE>

What am I doing wrong?

You have excluded “Articles” from being assigned a DOI within the DOI plugin settings, under section “Journal Content”. There, you have currently only enabled “Issues” and “Galleys”.

Almost certainly the Crossref plugin (since it is primarily concerned with Article DOIs) is flagging this as needing attention.

On the other hand, your screenshot appears to show that you have assigned a DOI to an article. That you were able to do this with the “Articles” option unchecked may be a bug. What specific version of OJS are you using? OJS 3.0.2 would be quite obsolete at this point.

Okay. I have found the Articles tab in the CrossRef Export plugin. When I click the checkbox next to an article and then click Submit, I get a Http 500 page not working error.
Do I need to create a different doi for the article to that if the galley?
By the way, articles was checked in the Journal Content on DOI Plugin Settings. I may have temporarily unchecked it but it was checked and now is.

The PHP error log would give you the details on where the code is failing with the 500 error.

With the settings you describe in the DOI Plugin Settings page, you will need to manually add a DOI to each Issue, Article, and Galley. Each DOI will need to be different and unique.

The Crossref plugin primarily considers Article DOIs, so my first guess on the 500 error would be that you have not manually assigned a DOI to the article being registered, but you would see the specific error message in your log.

Be sure that you are running a current version of OJS (e.g. 3.1.2-4) for current functionality and security.

There are some things I need help understanding.

How do I use existing dois assigned to galleys to find the articles? I’m concerned our previous articles will remain incorrectly assigned.

I think I have correctly assigned DOIs for the issue and the galley, but not it seems for articles. Is that correct?

Would I need to upload a fresh article in production and assign a new doi or just tick the boxes in the articles tab of the crossref plugin and click submit. But then I get the HTTPS 500 error.

Is this the php error log? public_html/murmurations/ojs/error_log
It only shows errors on 16th Jan.

(I take in what you are saying about upgrading but I need to sort out basic housekeeping first!)

I don’t have anything as old as 3.0.2 to reference, but I do have a test instance of 3.1.1-4 still hanging around.

There, you find the Galley DOIs by navigating to:
Submission -> Production -> Galleys -> (expand galley) -> Edit -> Identifiers
You find the Article DOIs by navigating to:
Submission -> Metadata -> Identifiers

Are you trying to connect your articles with existing DOIs that have already been registered via a former platform? That is the typical use-case for manually assigning DOIs. For brand new DOIs, it is typical to use OJS’s provided patterns or to create your own pattern for DOIs allocation.

If you are committed to manually assigning DOIs, you will need to go to each existing article and galley (assuming you want galley DOIs, which is uncommon with Crossref) and manually enter a DOI in the input box as I described “you find” above.

The location of your PHP error log will be determined by your system administrator or service provider. The “error_log” in the ojs directory is a possibility for this log. Any new 500-level error should write a new message to your PHP error log.

I followed these for production etc. They are the same identifier the DOI allocated to the galley shows as the same identifier for the production article.

Are you trying to connect your articles with existing DOIs that have already been registered via a former platform?

I have only used 3.02

That is the typical use-case for manually assigning DOIs. For brand new DOIs, it is typical to use OJS’s provided patterns or to create your own pattern for DOIs allocation.

I have always used the same DOI format. Manual assigning by adding a suffix when creating the identifier.

If you are committed to manually assigning DOIs, you will need to go to each existing article and galley (assuming you want galley DOIs, which is uncommon with Crossref) and manually enter a DOI in the input box as I described “you find” above.

I think I created the DOI for the final production article before uploading a galley. The galley seemed to assume the article’s identifier metadata.

The same DOI cannot be assigned to both a Galley and to an Article. With your current configuration you will need to manually assign a unique DOI to each.

I am still trying to resolve the dois not working.

  1. The articles are assigned the doi.The galleys have no specific doi.
  2. on the CrossRef plugin page it says Status: Not deposited.

Is something going wrong on CrossRef Plugin page?

I just increased the php.ini execution time to see if this made a difference and it did. Now I get this error when I try to deposit an article:

Failed to locate the main schema resource at ‘http://www.crossref.org/schema/deposit/crossref4.3.6.xsd’.

Invalid XML:

<?xml version="1.0" encoding="utf-8"?>

<doi_batch xmlns=“http://www.crossref.org/schema/4.3.6” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xmlns:jats=“http://www.ncbi.nlm.nih.gov/JATS1” xmlns:ai=“http://www.crossref.org/AccessIndicators.xsd” version=“4.3.6” xsi:schemaLocation=“http://www.crossref.org/schema/4.3.6 http://www.crossref.org/schema/deposit/crossref4.3.6.xsd”>

_1581506996 1581506996 Gail Simon gail.simon@murmurations.cloud Everything is Connected Press Murmurations: Journal of Transformative Systemic Practice Murmurations 2516-0052 12 31 2019 2 2 10.28963/2.2 http://murmurations.cloud/ojs/index.php/murmurations/issue/view/4 Editorial Gail Simon 01 03 2020 https://creativecommons.org/licenses/by-nc-nd/4.0/ 10.28963/2.2.1 http://murmurations.cloud/ojs/index.php/murmurations/article/view/88

Could not convert selected objects.

error in mEDRA export plugin

— Comment or Message —

Hi
Gives an error in converting files to xml.
http://jltll.ierf.ir
How to fix this problem? Gives the following message

Validation errors:

Failed to locate the main schema resource at ‘http://www.medra.org/schema/onix/DOIMetadata/2.0/ONIX_DOIMetadata_2.0.xsd’.
Invalid XML:

Sharif Pardazeshgar Danesh Co. - Customer Relation Manager,
Mokhberi Hadiseh
ghoroghi.sinaweb@gmail.com
mEDRA
202002281455
This dataset was exported with ojs2, version 3.1.0.1.

06
10.22034/jltll.v2i2.52
http://jltll.ierf.ir/index.php/home/article/view/52
Abstraction
Sharif Pardazeshgar Danesh Co. - Customer Relation Manager,
mEDRA

01
1-4-52

01
Journal of Language Teaching, Literature & Linguistics (JLTLL) - آموزش زبان، ادبیات و زبان شناسی

01
Osool Al-Dīn College & International E-Research Foundation (IERF)

IR

01
1

JD
01
Open Journal Systems (OJS)

07
26453428

JB

2
2
Vol 2 No 2: September 2019

4

49
75

01
A Review of Language Teachers’ Identity Development: A Focus on Cultural Identity Theories

1
A01
Hussein Meihami
Meihami, Hussein

PhD in Applied Linguistics, Department of Foreign Languages and Linguistics, Shiraz University, Iran

2
A01
Naser Rashidi
Rashidi, Naser

Professor of TEFL, Department of Foreign Languages and Linguistics Shiraz University, Iran

3
A01
Rahman Sahragard
Sahragard, Rahman

Professor of Applied Linguistics, Department of Foreign Languages and Linguistics Shiraz University, Iran

4
A01
Seyyed Ayatolah Razmjoo
Razmjoo, Seyyed Ayatolah

Professor of TEFL, Department of Foreign Languages and Linguistics Shiraz University, Iran

01
eng

23
Cultural Identity;Narratives;Professional Development;Positioning Theory

01

Teacher identity has been considered among the most influential key factors in the realm of teacher education. Studies on teacher identity help teacher educators to find new and conducive approaches to develop teacher identity in different contexts. This study is a theoretical review aiming to accentuate the recent underlying concepts of teacher identity, language teacher identity, and language teacher cultural identity. To those ends, we scrutinize the related issues such as the different perspectives about identity; key concepts in teacher identity including teacher professional identity, teacher motivation and identity, teacher emotion and identity, and narratives and teacher identity along with non-native English language teacher identify construction and reflexivity and language teacher identity. Moreover, a review of the related theories about cultural identity has been done and presented to address the most referred theories of cultural identity. Finally, some concluding remarks about the theoretical underpinnings of language teacher cultural identity have been discussed.

20190903

81

01
1-4

06
10.22034/jltll.v2i2

89

01
1-4-52-g67

Could not convert selected objects.

Hi @Ahmad_Mohamadi,

Someone will respond to your post at Error in mEDRA export plugin – please don’t post the same things in several places, as it clutters the forum.

Thanks,
Alec Smecher
Public Knowledge Project Team