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

[RFE] Enhanced file imports #121

Open
rromannissen opened this issue May 10, 2023 · 1 comment
Open

[RFE] Enhanced file imports #121

rromannissen opened this issue May 10, 2023 · 1 comment
Labels
Milestone

Comments

@rromannissen
Copy link
Contributor

CSV has some limitations in its capabilities, and it's not the most widespread spreadsheet format used by organizations worldwide. Even though the contents of a spreadsheet in other formats can be adapted to fit the CSV template that Konveyor uses, the process can be cumbersome especially when dealing with dependencies at scale, since Record Types are not the most practical approach.

To solve this, the proposal would be to include support for Excel (extensions .xlsx and .xls) and OpenDocument Format (extension .ods) spreadsheets. This would be aligned with the most used tools in the market, while easing the declaration of different record types (applications, dependencies and potentially more in the future) through the usage of dedicated tabs.

@Shevijacobson
Copy link

@rromannissen I wanted to clarify the scope of this issue regarding support for additional spreadsheet formats. From what I understand, the proposal suggests extending support to Excel (.xlsx, .xls) and OpenDocument Format (.ods), alongside CSV, to simplify working with large datasets and dependencies.

Could you please confirm whether the intention is to:

1.Support these new formats with a single sheet structure that mirrors the current CSV template—containing all data (Applications, Dependencies, etc.) in one unified sheet, but in a different file format.
Or, alternatively:
2. Leverage the unique capabilities of these formats to use multiple tabs, where each tab can represent different record types (e.g., one tab for Applications, another for Dependencies, etc.), rather than consolidating everything into one sheet.

Implementing the second approach would indeed streamline data organization but would differ in structure from the CSV template. It would be helpful to know which of these approaches aligns with the intended functionality.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants