RePEc Data Check for series repec:sja:journ1

Each night we check the validity of new and modified templates in the RePEc archives mirrored at EconPapers and run a link checker on a portion of the data. Data for series last updated 2024-03-07 21:26:00 GMT.

Data checked 2024-03-31 09:47:48 GMT, 1 errors and 30 warnings. 39 templates without errors.
Currently mirrored files for series (login with username datacheck and password repec)
Results for the sja archive.
Access statistics for repec:sja:journ1.

EconPapers listing for International Investment Law Journal From Societatea de Stiinte Juridice si Administrative (Society of Juridical and Administrative Sciences)
Contact information at EDIRC.
Bibliographic data for series maintained by Catalin-Silviu Sararu ().

rdf/redif-files, ReDIF compliance

Templates with errors can not be processed correctly and are dropped. Lines with warnings are ignored when the template is processed.
Consult the ReDIF documentation for further information.

Data checked 2024-03-31 09:47:48 GMT, 1 errors and 30 warnings. 39 templates without errors.
Correcting your data? Use our interactive check to validate your corrections.

Files with errors or warnings

Click to view problems in context (login with username datacheck and password repec)

2021vol.1Issue!00201.rdf 0 errors, 1 warnings
2022vol.2Issue!00201.rdf 0 errors, 24 warnings
2022vol.2Issue!00202.rdf 0 errors, 2 warnings
2023vol.3Issue!00201.rdf 1 errors, 0 warnings
2023vol.3Issue!00202.rdf 0 errors, 3 warnings

Errors

(2023vol.3Issue!00201.rdf, line 93): Invalid value 'http://http://www.investmentlaw.adjuris.ro/articole/an3v1/5.%20Sarghi%20Elena.pdf' of type <url> (attribute 'file-url', eval)

Warnings

(2021vol.1Issue!00201.rdf, line 79): Invalid value 'FIDIC Standard Forms of Contracts or National Contracts in Public Investment' of type <email> (attribute 'author-email', regex)
(2022vol.2Issue!00201.rdf, line 4): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 22): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 27): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 43): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 63): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 97): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00201.rdf, line 100): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00202.rdf, line 76): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2022vol.2Issue!00202.rdf, line 76): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2023vol.3Issue!00202.rdf, line 6): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2023vol.3Issue!00202.rdf, line 65): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
(2023vol.3Issue!00202.rdf, line 85): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.

URL check

URLs not checked