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:aic:saebjn

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 2025-01-07 08:04:00 GMT.
  • Data checked 2025-05-07 07:17:19 GMT, 20 errors and 81 warnings. 354 templates without errors.
  • Currently mirrored files for series (login with username datacheck and password repec)
  • Results for the aic archive.
  • Access statistics for repec:aic:saebjn.

EconPapers listing for Scientific Annals of Economics and Business (continues Analele Stiintifice) From Alexandru Ioan Cuza University, Faculty of Economics and Business Administration
Contact information at EDIRC.
Bibliographic data for series maintained by Sireteanu Napoleon-Alexandru ().

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-05-07 07:17:19 GMT, 20 errors and 81 warnings. 354 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. (2017_March_63_si_p89-107.rdf, line 6): Invalid (unknown) attribute 'purpose'. 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. (2019_September_66_3_p267!0020!2013!0020308-267!0020!2013!0020308.rdf, line 19): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:267 – 308-267 – 308:n:163' of type <documenthandle> (attribute 'handle', eval)
  3. (2019_September_66_3_p309!0020!2013!0020319-309!0020!2013!0020319.rdf, line 17): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:309 – 319-309 – 319:n:161' of type <documenthandle> (attribute 'handle', eval)
  4. (2019_September_66_3_p321!0020!2013!0020334-321!0020!2013!0020334.rdf, line 18): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:321 – 334-321 – 334:n:165' of type <documenthandle> (attribute 'handle', eval)
  5. (2019_September_66_3_p335!0020!2013!0020349-335!0020!2013!0020349.rdf, line 16): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:335 – 349-335 – 349:n:162' of type <documenthandle> (attribute 'handle', eval)
  6. (2019_September_66_3_p351!0020!2013!0020361-351!0020!2013!0020361.rdf, line 19): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:351 – 361-351 – 361:n:166' of type <documenthandle> (attribute 'handle', eval)
  7. (2019_September_66_3_p363!0020!2013!0020388-363!0020!2013!0020388.rdf, line 17): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:363 – 388-363 – 388:n:164' of type <documenthandle> (attribute 'handle', eval)
  8. (2019_September_66_3_p389!0020!2013!0020413-389!0020!2013!0020413.rdf, line 20): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:389 – 413-389 – 413:n:168' of type <documenthandle> (attribute 'handle', eval)
  9. (2019_September_66_3_p415!0020!2013!0020450-415!0020!2013!0020450.rdf, line 16): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:415 – 450-415 – 450:n:167' of type <documenthandle> (attribute 'handle', eval)
  10. (2023_December_70_4_p529-546.rdf, line 17): Required attribute 'title' is absent in template of type 'redif-article 1.0'
  11. (2024_March_71_1_p43-74.rdf, line 16): Required attribute 'title' is absent in template of type 'redif-article 1.0'
  12. (Argyrios!0020D.!0020Kolokontes_2019_September_vol_66_p267!0020!2013!0020308.rdf, line 19): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:267 – 308-267 – 308:n:150' of type <documenthandle> (attribute 'handle', eval)
  13. (Cristi!0020Spulbar_2019_September_vol_66_p351!0020!2013!0020361.rdf, line 19): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:351 – 361-351 – 361:n:153' of type <documenthandle> (attribute 'handle', eval)
  14. (Gouranga!0020Gopal!0020Das_2019_September_vol_66_p415!0020!2013!0020450.rdf, line 16): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:415 – 450-415 – 450:n:154' of type <documenthandle> (attribute 'handle', eval)
  15. (Ion!0020Radu!0020Zili!0219teanu_2019_September_vol_66_p389!0020!2013!0020413.rdf, line 20): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:389 – 413-389 – 413:n:155' of type <documenthandle> (attribute 'handle', eval)
  16. (Kas!0131m!0020Kirac!0131_2019_September_vol_66_p335!0020!2013!0020349.rdf, line 16): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:335 – 349-335 – 349:n:149' of type <documenthandle> (attribute 'handle', eval)
  17. (Ruslan!0020Biloskurskyy_2019_September_vol_66_p321!0020!2013!0020334.rdf, line 18): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:321 – 334-321 – 334:n:152' of type <documenthandle> (attribute 'handle', eval)
  18. (Serkan!0020Aras_2019_September_vol_66_p363!0020!2013!0020388.rdf, line 17): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:363 – 388-363 – 388:n:151' of type <documenthandle> (attribute 'handle', eval)
  19. (Shimon!0020ELBAZ_2017_January_vol_63_p89.rdf, line 6): Invalid (unknown) attribute 'purpose'. 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.
  20. (Yilmaz!0020Bayar_2019_September_vol_66_p309!0020!2013!0020319.rdf, line 17): Invalid value 'RePEc:aic:saebjn:v:66:y:2019:i:3:p:309 – 319-309 – 319:n:148' of type <documenthandle> (attribute 'handle', eval)

Warnings

  1. (!017Daneta!0020Rylkov!00E1_2017_December_vol_64_p29.rdf, line 4): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  2. (!017Daneta!0020Rylkov!00E1_2017_December_vol_64_p29.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  3. (2017_December_64_4_p411-422.rdf, line 6): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  4. (2017_December_64_4_p411-422.rdf, line 6): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  5. (2017_December_64_si_p29-40.rdf, line 4): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  6. (2017_December_64_si_p29-40.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  7. (2017_December_64_si_p71-83.rdf, line 5): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  8. (2017_March_63_si_p71-87.rdf, line 2): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  9. (2019_December_66_si_p149-172.rdf, line 2): Bad Windows-1252 character \x{81}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  10. (2019_December_66_si_p149-172.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  11. (2019_September_66_si_p5-23.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  12. (2019_September_66_si_p5-23.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  13. (2019_September_66_si_p91-112.rdf, line 1): Long author-name 'Amélia Maria Pinto da Cunha Brandão', possibly multiple authors
  14. (2020_December_67_si_p33-55.rdf, line 1): Long author-name 'Amélia Maria Pinto da Cunha Brandão', possibly multiple authors
  15. (2021_December_68_4_p405-419.rdf, line 8): Bad Windows-1252 character \x{81}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  16. (2021_December_68_si_p35-52.rdf, line 2): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  17. (2021_June_68_2_p195-232.rdf, line 5): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  18. (2021_June_68_2_p195-232.rdf, line 5): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  19. (2021_March_68_1_p75-96.rdf, line 5): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  20. (2021_September_68_3_p379-404.rdf, line 2): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  21. (2022_June_69_3_p377-392.rdf, line 3): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  22. (2022_June_69_3_p377-392.rdf, line 5): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  23. (2022_September_69_3_p477-500.rdf, line 3): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  24. (2023_June_70_2_p235-262.rdf, line 6): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  25. (2024_December_71_4_p497-518.rdf, line 8): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  26. (2024_September_71_3_p417-447.rdf, line 8): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  27. (Am!00E9lia!0020!0020Brand!00E3o_2022_March_vol_69_p1.rdf, line 10): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  28. (Am!00E9lia!0020!0020Brand!00E3o_2022_March_vol_69_p1.rdf, line 10): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  29. (Am!00E9lia!0020!0020Brand!00E3o_2022_March_vol_69_p1.rdf, line 10): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  30. (Am!00E9lia!0020Maria!0020Pinto!0020da!0020Cunha!0020Brand!00E3o_2019_July_vol_66_p91.rdf, line 1): Long author-name 'Amélia Maria Pinto da Cunha Brandão', possibly multiple authors
  31. (Am!00E9lia!0020Maria!0020Pinto!0020da!0020Cunha!0020Brand!00E3o_2019_June_vol_66_p253.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  32. (Am!00E9lia!0020Maria!0020Pinto!0020da!0020Cunha!0020Brand!00E3o_2019_June_vol_66_p253.rdf, line 1): Long author-name 'Amélia Maria Pinto da Cunha Brandão', possibly multiple authors
  33. (Am!00E9lia!0020Maria!0020Pinto!0020da!0020Cunha!0020Brand!00E3o_2020_December_vol_67_p33.rdf, line 1): Long author-name 'Amélia Maria Pinto da Cunha Brandão', possibly multiple authors
  34. (Argyrios!0020D.!0020Kolokontes_2020_June_vol_67_p193.rdf, line 8): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  35. (Argyrios!0020D.!0020Kolokontes_2020_June_vol_67_p193.rdf, line 10): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  36. (Athanasios!0020L.!0020Athanasenas_2018_June_vol_65_p171.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  37. (Athanasios!0020L.!0020Athanasenas_2018_June_vol_65_p171.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  38. (Athanasios!0020L.!0020Athanasenas_2018_June_vol_65_p171.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  39. (Athanasios!0020L.!0020Athanasenas_2018_June_vol_65_p171.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  40. (Athanasios!0020L.!0020Athanasenas_2018_June_vol_65_p171.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  41. (Athanasios!0020L.!0020Athanasenas_2018_June_vol_65_p171.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  42. (Blas!0020D!00CDaz!0020Le!00F3n_2021_November_vol_68_p35.rdf, line 2): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  43. (Bruno!0020Duarte!0020Abreu!0020Freitas_2020_December_vol_67_p495.rdf, line 4): Bad Windows-1252 character \x{81}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  44. (Bruno!0020Duarte!0020Abreu!0020Freitas_2020_September_vol_67_p363.rdf, line 4): Bad Windows-1252 character \x{81}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  45. (Costic!0103!0020MIHAI_2016_March_vol_63_p117.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  46. (Costic!0103!0020MIHAI_2016_March_vol_63_p117.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  47. (Costic!0103!0020MIHAI_2016_March_vol_63_p117.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  48. (Cristian!0020Constantin!0020Popescu_2022_June_vol_69_p377.rdf, line 3): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  49. (Cristian!0020Constantin!0020Popescu_2022_June_vol_69_p377.rdf, line 5): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  50. (David!0020PROCH!00C1ZKA_2017_March_vol_64_p59.rdf, line 2): Bad Windows-1252 character \x{81}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  51. (Elena!0020Mielcova_2017_December_vol_64_p71.rdf, line 5): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  52. (Emrah!0020Gulay_2018_June_vol_65_p159.rdf, line 5): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  53. (Francisco!0020Flores!0020Mu!00F1oz_2018_December_vol_65_p497.rdf, line 5): Bad Windows-1252 character \x{81}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  54. (Goran!0020Karanovic_2018_March_vol_65_p1.rdf, line 6): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  55. (Goran!0020Karanovic_2018_March_vol_65_p1.rdf, line 6): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  56. (Ignacio!0020MART!00CDNEZ_2017_January_vol_63_p71.rdf, line 2): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  57. (Ivana!0020FOSI!0106_2017_September_vol_64_p339.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  58. (Ivana!0020FOSI!0106_2017_September_vol_64_p339.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  59. (Ivana!0020FOSI!0106_2017_September_vol_64_p339.rdf, line 9): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  60. (Ivana!0020FOSI!0106_2017_September_vol_64_p339.rdf, line 9): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  61. (Juan!0020Jos!00E9!0020Garc!00EDa!0020del!0020Hoyo_2019_July_vol_66_p5.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  62. (Juan!0020Jos!00E9!0020Garc!00EDa!0020del!0020Hoyo_2019_July_vol_66_p5.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  63. (Larysa!0020Yakymova_2018_December_vol_65_p385.rdf, line 5): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  64. (Lejla!0020Terzi!0107_2022_August_vol_69_p477.rdf, line 3): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  65. (Letife!0020!00D6zdemir_2021_October_vol_68_p405.rdf, line 8): Bad Windows-1252 character \x{81}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  66. (Luis!0020!00C1ngel!0020Hierro_2019_December_vol_66_p149.rdf, line 2): Bad Windows-1252 character \x{81}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  67. (Luis!0020!00C1ngel!0020Hierro_2019_December_vol_66_p149.rdf, line 7): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  68. (Mara!0020del!0020Baldo_2017_December_vol_64_p411.rdf, line 6): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  69. (Mara!0020del!0020Baldo_2017_December_vol_64_p411.rdf, line 6): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  70. (Marcin!0020Wi!015Bniewski_2020_December_vol_67_p437.rdf, line 3): Bad Windows-1252 character \x{81}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  71. (Marcin!0020Wi!015Bniewski_2020_December_vol_67_p437.rdf, line 6): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  72. (Marina!0020Fa!010Fo!0161_2018_September_vol_65_p269.rdf, line 2): Bad Windows-1252 character \x{8F}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  73. (Martin!0020PA!017DICK!00DD_2017_June_vol_64_p155.rdf, line 2): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  74. (Martina!0020Ju!0159!00EDkov!00E1_2022_December_vol_69_p539.rdf, line 6): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  75. (Mihaela!0020Onofrei_2023_February_vol_70_p33.rdf, line 3): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  76. (Mykolas!0020Navickas_2019_March_vol_66_p1.rdf, line 3): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  77. (Ngoc!0020Bao!0020Vuong_2020_June_vol_67_p157.rdf, line 6): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  78. (Sorin!0020Gabriel!0020ANTON_2016_November_vol_63_p311.rdf, line 5): Bad Windows-1252 character \x{9D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  79. (Zuzana!0020Brin!010D!00EDkov!00E1_2018_December_vol_65_p427.rdf, line 2): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  80. (Zuzana!0020Lu!0161!0148!00E1kov!00E1_2019_March_vol_66_p85.rdf, line 3): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.
  81. (Zuzana!0020Lu!0161!0148!00E1kov!00E1_2019_March_vol_66_p85.rdf, line 5): Bad Windows-1252 character \x{8D}. Consider using Unicode, see "Unicode" in the archive maintainers FAQ.

URL check

URLs not checked

 

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