Consolidated Shiny Items

[TNRiley]

Edit this comment to add further items

Higher Priority

• Update About and Use Cases text on the Home tab

• Add a table similar to the table posted on the discussion page deduplication Q/A in order to show users the various ways duplicates are being identified.

• Revamp Manual deduplication UX - no current idea on what this SHOULD look like, current UX is difficult to understand. Potentially limit to key fields, one row per record, -- the filter here could be adjusted for a quick fix

• Provide further instruction on manual deduplication tab and provide information on how metadata will be merged IF records are selected as duplicates - for example - what metadata will be kept in cases where both records have metadata. - this may also lead to further functionality development for allowing users to select which fields they want to keep from between multiple records.

• In Shiny the summary table and individual record table do not reflect the user's source name, but retains the file name - ensure these are corrected (mixed results on this, not happening on all uploads - must depend on file name...)

• CSV export has duplicate columns exporting same data cite_source = source, cite_lable = label, etc.

• turn warnings in tables into Shiny popups, when correct labels are missing (old issue, check to see if complete)

Lower Priority

• on upload if an .ris file has the phrase bib (ex. ASFAbibfix.ris, DIMbibfix.ris) The source cuts out the "bib" as well as the character prior to bib (ex. associated with above ex. ASFfix, DIfix). Assume this is due to .bib files being a file format that can be uploaded and our automating of source names to remove .bib or .ris - very low priority

Questions

• Will users have the option to select the T/F only_key_fields argument when reading in citations? This may be needed if folks have data they want to retain.
• RIS export is broken due to mapping additions. Can we build in an option for users to select the mapping of ID, source, label fields to the custom metadata fields they want?

Check off items and move to complete - Add a comment on the action taken as needed

Complete

• Examine issue where after removing duplicates manually, users must click the proceed without manual deduplication in order to see visualizations.
• Examine issue where you cannot see text in the textbox when adding or changing metadata in the editable fields after upload.
• Examine issue where tables begin to be generated when you go to the table tab, this happens without the user clicking on the generate table button.

[LukasWallrich]

• Call current tables
• Remove library() calls

[LukasWallrich]

@TNRiley I believe I fixed two of the points above - can you check? The tables are still work in progress, I hope to get that sorted in the morning ...

[TNRiley]

@TNRiley I believe I fixed two of the points above - can you check? The tables are still work in progress, I hope to get that sorted in the morning ...

Driving tonight, but will check when I have a chance.🤘

[LukasWallrich]

Fixed some more of the points - but we also need:

• turn warnings in tables into Shiny popups, when correct labels are missing

[TNRiley]

• add a tab for the pase count table after the search summary. These are used for different use cases.

[TNRiley]

• Allow users to select which metadata fields they want to see during the manual deduplication process. Currently, the view cuts fields off pretty significantly
• allow users to expand columns horizontally for better readability - otherwise wrap text in specific fields so users can see the all metadata in the field (ex. title, author, journal)

[rootsandberries]

• Switch tabs on Table page so View summary table is first. The instinct is to click the generate table button on the first tab (which is currently the record-level table) leading to a very long process.
• Consider option on manual deduplication page to show more than just 10 records (or whatever it is currently set at) on the page, and add Select All.