lynx   »   [go: up one dir, main page]

  EconPapers    
Economics at your fingertips  
 

RePEc Data Check for series repec:ifs:cemmap

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 2021-12-17 12:43:44 GMT.
  • Data checked 2025-03-22 11:21:19 GMT, 5 errors and 73 warnings. 877 templates without errors.
  • 877 URLs checked 2025-09-19 13:03:22 GMT, 852 errors, 1 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 ifs archive.
  • Access statistics for repec:ifs:cemmap.

EconPapers listing for CeMMAP working papers From Centre for Microdata Methods and Practice, Institute for Fiscal Studies
The Institute for Fiscal Studies 7 Ridgmount Street LONDON WC1E 7AE.
Contact information at EDIRC.

Bibliographic data for series maintained by Emma Hyman ().


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 11:21:19 GMT, 5 errors and 73 warnings. 877 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. (cemmap.rdf, line 3235): Invalid (unknown) attribute 'download'. Any 'word:' combination at the start of a line is interpreted as an attribute. Put a space at the beginning of the line to avoid this error.
  2. (cemmap.rdf, line 7493): Invalid value 'RePEc:ifs:cemmap:' of type <documenthandle> (attribute 'handle', eval)
  3. (cemmap.rdf, line 7514): Invalid value 'RePEc:ifs:cemmap:' of type <documenthandle> (attribute 'handle', eval)
  4. (cemmap.rdf, line 8522): Invalid value 'RePEc:ifs:cemmap:' of type <documenthandle> (attribute 'handle', eval)
  5. (cemmap.rdf, line 11469): Invalid value 'RePEc:ifs:cemmap:' of type <documenthandle> (attribute 'handle', eval)

Warnings

  1. (cemmap.rdf, line 3335): Key attribute 'author-name' has an empty value
  2. (cemmap.rdf, line 6434): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  3. (cemmap.rdf, line 6434): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  4. (cemmap.rdf, line 7802): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  5. (cemmap.rdf, line 7802): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  6. (cemmap.rdf, line 7808): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  7. (cemmap.rdf, line 7885): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  8. (cemmap.rdf, line 7885): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  9. (cemmap.rdf, line 7991): Control character \x{15} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  10. (cemmap.rdf, line 7991): Control character \x{15} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  11. (cemmap.rdf, line 7991): Control character \x{01} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  12. (cemmap.rdf, line 7991): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  13. (cemmap.rdf, line 8061): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  14. (cemmap.rdf, line 8061): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  15. (cemmap.rdf, line 8061): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  16. (cemmap.rdf, line 8061): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  17. (cemmap.rdf, line 8065): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  18. (cemmap.rdf, line 8065): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  19. (cemmap.rdf, line 8116): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  20. (cemmap.rdf, line 8116): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  21. (cemmap.rdf, line 8116): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  22. (cemmap.rdf, line 8116): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  23. (cemmap.rdf, line 8116): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  24. (cemmap.rdf, line 8176): Control character \x{13} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  25. (cemmap.rdf, line 8180): Control character \x{13} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  26. (cemmap.rdf, line 8426): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  27. (cemmap.rdf, line 8426): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  28. (cemmap.rdf, line 8430): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  29. (cemmap.rdf, line 8486): Control character \x{13} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  30. (cemmap.rdf, line 8754): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  31. (cemmap.rdf, line 8810): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  32. (cemmap.rdf, line 8903): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  33. (cemmap.rdf, line 8999): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  34. (cemmap.rdf, line 8999): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  35. (cemmap.rdf, line 8999): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  36. (cemmap.rdf, line 8999): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  37. (cemmap.rdf, line 8999): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  38. (cemmap.rdf, line 8999): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  39. (cemmap.rdf, line 8999): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  40. (cemmap.rdf, line 8999): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  41. (cemmap.rdf, line 9139): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  42. (cemmap.rdf, line 9139): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  43. (cemmap.rdf, line 9466): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  44. (cemmap.rdf, line 9466): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  45. (cemmap.rdf, line 9466): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  46. (cemmap.rdf, line 10421): Control character \x{01} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  47. (cemmap.rdf, line 11007): An invalid JEL code used 'H34'
  48. (cemmap.rdf, line 11976): Control character \x{1A} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  49. (cemmap.rdf, line 11976): Control character \x{19} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  50. (cemmap.rdf, line 12051): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  51. (cemmap.rdf, line 12076): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  52. (cemmap.rdf, line 12181): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  53. (cemmap.rdf, line 12181): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  54. (cemmap.rdf, line 12454): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  55. (cemmap.rdf, line 12454): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  56. (cemmap.rdf, line 12545): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  57. (cemmap.rdf, line 12545): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  58. (cemmap.rdf, line 12640): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  59. (cemmap.rdf, line 12729): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  60. (cemmap.rdf, line 13053): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  61. (cemmap.rdf, line 13053): Control character \x{01} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  62. (cemmap.rdf, line 13053): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  63. (cemmap.rdf, line 13053): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  64. (cemmap.rdf, line 13053): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  65. (cemmap.rdf, line 13053): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  66. (cemmap.rdf, line 13053): Control character \x{12} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  67. (cemmap.rdf, line 13098): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  68. (cemmap.rdf, line 13098): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  69. (cemmap.rdf, line 13098): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  70. (cemmap.rdf, line 13692): Control character \x{19} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  71. (cemmap.rdf, line 13692): Control character \x{19} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  72. (cemmap.rdf, line 15608): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  73. (cemmap.rdf, line 15874): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.

 

URL check

877 URLs checked 2025-09-19 13:03:22 GMT, 852 errors, 1 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:ifs:cemmap

Warnings

Warnings indicate possible problems or errors. Warnings are issued for the following conditions:

  • Redirects: Redirects are used to indicate that a resource has moved to a new location. This is a legitimate use but the redirect is unlikely to stay in place forever so it is a good idea to update the information before the redirect is lost. Unfortunately many webservers are misconfigured to give a redirection status code (3xx) when it should send an error status code (usually 401, 403 or 404). The URL needs correcting if you follow the link and end up on a page mentioning an error code or that the page could not be found.
  • Inconsistent file format: The server indicates that this is a html-document but the extension of the file name is inconsistent with this. This could be a spurious warning but the most likely source of this is a bad URL and a server that is misconfigured to send a '200 OK' response together with a custom error page. If so, the URL should be corrected in the template.

Warnings in series repec:ifs:cemmap

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