Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write out final RIS file #19

Closed
LukasWallrich opened this issue Mar 15, 2022 · 2 comments
Closed

Write out final RIS file #19

LukasWallrich opened this issue Mar 15, 2022 · 2 comments
Assignees
Labels
Internal Internal functionality Output Data output Shiny Application
Milestone

Comments

@LukasWallrich
Copy link
Collaborator

Once deduplication is done, a final RIS file should be written out. All sources that the record was found in should be included in the database field - possibly as a JSON, or simply comma separated?

@LukasWallrich
Copy link
Collaborator Author

Also allow download as a csv file to facilitate future analyses

@TNRiley TNRiley added this to the MVP milestone Sep 8, 2022
@TNRiley TNRiley added Output Data output Internal Internal functionality Shiny Application labels Sep 8, 2022
@LukasWallrich
Copy link
Collaborator Author

I have now added export_csv() which allows users to write out a csv file for further analyses - please have a look, but that seems fine.

For export_ris(), we would like to use synthesisr, but that currently does not allow for the export of custom fields (a way to do that seems half-implemented - I raised an issue). For now, I overwrote one of their functions from within our package ... that is not particularly robust and will likely be rejected by CRAN, but it should be good enough for the MVP.

We still need to decide what fields to use. For now, the function defaults to DB for source, C7 for label and C8 for string (I thought the last two custom fields would be least likely to clash with other info, and Wikipedia at least only lists 8). According to synthesisr, C7 is used by some databases for an "article number" - but we can probably live with that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Internal Internal functionality Output Data output Shiny Application
Projects
None yet
Development

No branches or pull requests

5 participants