You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am studying the possibility of using this open data in scientific journals, conference abstracts, academic theses, and presentations. The license specifies that the logo should be included when using the data, but I have some questions regarding specific contexts.
In scientific publications such as journal articles and conference abstracts, it is uncommon to include logos. Instead, proper citation or reference to the data is typically provided. However, in theses, presentations, and notebooks, it would be possible to include the logo where appropriate.
Could you clarify whether a proper reference or citation would suffice for journals and abstracts, and whether there is specific guidance on how to handle the license requirements in these various academic contexts?
Thank you for your guidance and clarification.
Best regards,
Tiago Fernandes
The text was updated successfully, but these errors were encountered:
Hello,
I am studying the possibility of using this open data in scientific journals, conference abstracts, academic theses, and presentations. The license specifies that the logo should be included when using the data, but I have some questions regarding specific contexts.
In scientific publications such as journal articles and conference abstracts, it is uncommon to include logos. Instead, proper citation or reference to the data is typically provided. However, in theses, presentations, and notebooks, it would be possible to include the logo where appropriate.
Could you clarify whether a proper reference or citation would suffice for journals and abstracts, and whether there is specific guidance on how to handle the license requirements in these various academic contexts?
Thank you for your guidance and clarification.
Best regards,
Tiago Fernandes
The text was updated successfully, but these errors were encountered: