lynx   »   [go: up one dir, main page]
  EconPapers    
Economics at your fingertips  

EconPapers Home
About EconPapers

Working Papers
Journal Articles
Books and Chapters
Software Components

Authors

JEL codes
New Economics Papers

Data Check Home

Advanced Search


EconPapers FAQ
Archive maintainers FAQ
Cookies at EconPapers

The RePEc blog
The RePEc plagiarism page

 

RePEc Data Check for series repec:bcc:wpaper

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 2018-09-03 13:19:29 GMT.
  • Data checked 2025-03-22 10:02:39 GMT, 1 errors and 38 warnings. 93 templates without errors.
  • 93 URLs checked 2022-08-07 13:04:49 GMT, 93 errors, 0 warnings
    Papers with bad full text links (File-URL) are not included in NEP.
  • Currently mirrored files for series (login with username datacheck and password repec)
  • Results for the bcc archive.
  • Access statistics for repec:bcc:wpaper.

EconPapers listing for Working Papers From BC3
Bibliographic data for series maintained by Sergio Henrique Faria ().

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 2025-03-22 10:02:39 GMT, 1 errors and 38 warnings. 93 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)

Errors

  1. (redifWP2018-02.rdf, line 31): Invalid value 'RePEc:bcc:wpaper:WP 2018-02' of type <documenthandle> (attribute 'handle', eval)

Warnings

  1. (redif2009-01.rdf, line 15): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  2. (redif2011-10.rdf, line 15): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  3. (redif2012-04.rdf, line 12): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  4. (redif2012-06.rdf, line 9): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  5. (redif2012-06.rdf, line 9): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  6. (redif2012-07.rdf, line 15): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  7. (redif2012-09.rdf, line 11): Key attribute 'author-name' has an empty value
  8. (redif2012-09.rdf, line 16): Invalid value 'October 2012' of type <date> (attribute 'creation-date', eval). Dates should be YYYY-MM-DD, YYYY-MM or YYYY.
  9. (redif2012-10.rdf, line 25): Invalid value 'October 2012' of type <date> (attribute 'creation-date', eval). Dates should be YYYY-MM-DD, YYYY-MM or YYYY.
  10. (redif2012-11.rdf, line 10): Invalid value 'October 2012' of type <date> (attribute 'creation-date', eval). Dates should be YYYY-MM-DD, YYYY-MM or YYYY.
  11. (redif2012-11.rdf, line 13): Invalid MIME-type used: 'application/text-plain:formatted'
  12. (redif2012-12.rdf, line 10): Invalid value 'October 2012' of type <date> (attribute 'creation-date', eval). Dates should be YYYY-MM-DD, YYYY-MM or YYYY.
  13. (redif2012-13.rdf, line 13): Invalid value 'October 2012' of type <date> (attribute 'creation-date', eval). Dates should be YYYY-MM-DD, YYYY-MM or YYYY.
  14. (redif2012-14.rdf, line 16): Invalid MIME-type used: 'application/text-plain:formatted'
  15. (redif2013-01.rdf, line 12): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  16. (redif2013-01.rdf, line 12): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  17. (redif2013-04.rdf, line 16): Invalid MIME-type used: 'application/text-plain:formatted'
  18. (redif2013-05.rdf, line 16): Invalid MIME-type used: 'application/text-plain:formatted'
  19. (redif2013-06.rdf, line 22): Invalid MIME-type used: 'application/text-plain:formatted'
  20. (redif2013-07.rdf, line 16): Invalid MIME-type used: 'application/text-plain:formatted'
  21. (redif2013-08.rdf, line 17): Invalid MIME-type used: 'application/text-plain:formatted'
  22. (redif2013-11.rdf, line 15): Invalid MIME-type used: 'application/text-plain:formatted'
  23. (redif2013-13.rdf, line 9): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  24. (redif2013-13.rdf, line 9): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  25. (redif2013-14.rdf, line 17): Invalid MIME-type used: 'application/text-plain:formatted'
  26. (redif2014-04.rdf, line 24): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  27. (redif2014-05.rdf, line 17): Key attribute 'author-name' has an empty value
  28. (redif2014-06.rdf, line 8): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  29. (redif2015-03.rdf, line 19): Invalid MIME-type used: 'application/download'
  30. (redif2016-01.rdf, line 16): Invalid MIME-type used: 'application/download'
  31. (redif2016-02.rdf, line 20): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  32. (redif2016-02.rdf, line 22): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  33. (redif2016-02.rdf, line 33): Invalid MIME-type used: 'application/download'
  34. (redif2016-03.rdf, line 16): Invalid MIME-type used: 'application/download'
  35. (redif2016-05.rdf, line 18): Invalid MIME-type used: 'application/download'
  36. (redif2017-01.rdf, line 18): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  37. (redif2018-02.rdf, line 25): Invalid value '2018-July' of type <date> (attribute 'creation-date', eval). Dates should be YYYY-MM-DD, YYYY-MM or YYYY.
  38. (redifWP2018-02.rdf, line 25): Invalid value '2018-July' of type <date> (attribute 'creation-date', eval). Dates should be YYYY-MM-DD, YYYY-MM or YYYY.
 

URL check

93 URLs checked 2022-08-07 13:04:49 GMT, 93 errors, 0 warnings
Papers with bad full text links (File-URL) are not included in NEP.

Errors

Errors indicate bad URLs, the URL should be corrected or removed from the template if the file is no longer available.

  • '500' type errors might be temporary, a count is given for the error if it has persisted for more than one week. In this case the cause (which is typically a DNS error or a problem with the server holding the file) should be investigated and the error corrected.
  • 'bad file descriptor' is a cryptic error message that most likely means that, for a https link, that there is a problem with the SSL certificate. It might be expired or an intermediate certificate is missing from the server.
  • Occassionally an error link might work when you click on it in the browser. Hopefully this is because the error has been resolved. If this condition persists and the links have been checked again (the links for a series are rechecked roughly once a week) here are some likely explanations for the inconsistency:
    • Accesses from the outside are blocked but allowed from within the local network. This needs correcting.
    • Your web server responds differently to HEAD and GET requests, which it should not. We use HEAD requests to check the links because it puts a lighter load on your web server and saves on network bandwidth. Suitable reading for your web server administrator is sections 4.1 and 4.3.2 in RFC 7231 which specify how web servers should behave. If your administrator insists on not implementing HEAD properly he/she should at least configure the server to return a sensible response such as "405 Method Not Allowed" or "501 Not Implemented" so that we can use other methods (a conditional GET) to check the link.
    • The relatively large number of accesses made by the link checker has been identified as suspect by your web server. If so white listing the User-Agent of the link checker should resolve the issue. The User-Agent string is currently "RePEc link checker (https://EconPapers.repec.org/check/)" and you should match on "RePEc link checker" as this will not change.

Errors in series repec:bcc:wpaper

RePEc
This site is part of RePEc and all the data displayed here is part of the RePEc data set.

Is your work missing from RePEc? Here is how to contribute.

Questions or problems? Check the EconPapers FAQ or send mail to .

Örebro UniversityEconPapers is hosted by the School of Business at Örebro University.

 
Page updated 2025-06-17
            
Лучший частный хостинг