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:aeg:report

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 2020-06-30 16:59:35 GMT.
  • Data checked 2025-03-22 09:53:19 GMT, 1 errors and 66 warnings. 92 templates without errors.
  • 92 URLs checked 2025-09-23 13:55:04 GMT, 29 errors, 63 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 aeg archive.
  • Access statistics for repec:aeg:report.

EconPapers listing for DIAG Technical Reports From Department of Computer, Control and Management Engineering, Universita' degli Studi di Roma "La Sapienza"
Contact information at EDIRC.
Bibliographic data for series maintained by Antonietta Angelica Zucconi ( this e-mail address is bad, please contact ).

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 09:53:19 GMT, 1 errors and 66 warnings. 92 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. (repaeg2012-01.rdf, line 1028): Required attribute 'handle' is absent in template of type 'redif-paper 1.0'

Warnings

  1. (repaeg2012-01.rdf, line 538): Control character \x{1B} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  2. (repaeg2012-01.rdf, line 538): Control character \x{1C} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  3. (repaeg2012-01.rdf, line 538): Control character \x{1C} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  4. (repaeg2012-01.rdf, line 538): Control character \x{1B} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  5. (repaeg2012-01.rdf, line 538): Control character \x{1B} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  6. (repaeg2012-01.rdf, line 612): Invalid value 'federico.papa@iasi.cnr.it,' of type <email> (attribute 'author-email', regex)
  7. (repaeg2012-01.rdf, line 708): Control character \x{03} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  8. (repaeg2012-01.rdf, line 709): Control character \x{1C} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  9. (repaeg2012-01.rdf, line 709): Control character \x{1B} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  10. (repaeg2012-01.rdf, line 709): Control character \x{1B} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  11. (repaeg2012-01.rdf, line 709): Control character \x{1B} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  12. (repaeg2012-01.rdf, line 910): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  13. (repaeg2012-01.rdf, line 1022): Control character \x{1C} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  14. (repaeg2012-01.rdf, line 1022): Control character \x{1C} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  15. (repaeg2012-01.rdf, line 1028): Control character \x{03} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  16. (repaeg2012-01.rdf, line 1278): Control character \x{03} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  17. (repaeg2012-01.rdf, line 1290): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  18. (repaeg2012-01.rdf, line 1339): Control character \x{1B} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  19. (repaeg2012-01.rdf, line 1339): Control character \x{1B} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  20. (repaeg2012-01.rdf, line 1339): Control character \x{1C} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  21. (repaeg2012-01.rdf, line 1339): Control character \x{1B} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  22. (repaeg2012-01.rdf, line 1414): Control character \x{13} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  23. (repaeg2012-01.rdf, line 1421): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  24. (repaeg2012-01.rdf, line 1421): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  25. (repaeg2012-01.rdf, line 1421): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  26. (repaeg2012-01.rdf, line 1427): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  27. (repaeg2012-01.rdf, line 1427): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  28. (repaeg2012-01.rdf, line 1552): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  29. (repaeg2012-01.rdf, line 1552): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  30. (repaeg2012-01.rdf, line 1658): Control character \x{13} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  31. (repaeg2012-01.rdf, line 1665): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  32. (repaeg2012-01.rdf, line 1665): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  33. (repaeg2012-01.rdf, line 1665): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  34. (repaeg2012-01.rdf, line 1665): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  35. (repaeg2012-01.rdf, line 1665): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  36. (repaeg2012-01.rdf, line 1665): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  37. (repaeg2012-01.rdf, line 1671): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  38. (repaeg2012-01.rdf, line 1671): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  39. (repaeg2012-01.rdf, line 1706): Invalid value 'gianmaria.leo/mauro.piacentini@sabre.com' of type <email> (attribute 'author-email', regex)
  40. (repaeg2012-01.rdf, line 1780): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  41. (repaeg2012-01.rdf, line 1895): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  42. (repaeg2012-01.rdf, line 1921): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  43. (repaeg2012-01.rdf, line 1921): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  44. (repaeg2012-01.rdf, line 1921): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  45. (repaeg2012-01.rdf, line 1949): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  46. (repaeg2012-01.rdf, line 2163): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  47. (repaeg2012-01.rdf, line 2191): Bad Windows-1252 character \x{81}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  48. (repaeg2012-01.rdf, line 2197): Control character \x{03} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  49. (repaeg2012-01.rdf, line 2212): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  50. (repaeg2012-01.rdf, line 2235): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  51. (repaeg2012-01.rdf, line 2344): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  52. (repaeg2012-01.rdf, line 2350): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  53. (repaeg2012-01.rdf, line 2350): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  54. (repaeg2012-01.rdf, line 2350): Control character \x{03} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  55. (repaeg2012-01.rdf, line 2367): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  56. (repaeg2012-01.rdf, line 2367): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  57. (repaeg2012-01.rdf, line 2367): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  58. (repaeg2012-01.rdf, line 2367): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  59. (repaeg2012-01.rdf, line 2367): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  60. (repaeg2012-01.rdf, line 2469): Control character \x{13} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  61. (repaeg2012-01.rdf, line 2491): Control character \x{0E} dropped. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  62. (repaeg2012-01.rdf, line 2616): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  63. (repaeg2012-01.rdf, line 2616): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  64. (repaeg2012-01.rdf, line 2616): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  65. (repaeg2012-01.rdf, line 2616): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  66. (repaeg2012-01.rdf, line 2690): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
 

URL check

92 URLs checked 2025-09-23 13:55:04 GMT, 29 errors, 63 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:aeg:report

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:aeg:report

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-09-24
            
Лучший частный хостинг