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

[Feature Request] Datamap RO-Crate parser #365

Open
HLWeil opened this issue Jun 5, 2024 · 1 comment
Open

[Feature Request] Datamap RO-Crate parser #365

HLWeil opened this issue Jun 5, 2024 · 1 comment
Assignees
Labels
Type: Feature Request This item is confirmed by the maintainers to be a request for a new feature

Comments

@HLWeil
Copy link
Member

HLWeil commented Jun 5, 2024

connected to #357

@github-actions github-actions bot added the Status: Needs Triage This item is up for investigation. label Jun 5, 2024
@HLWeil HLWeil moved this to Ready in ARCStack Jun 5, 2024
@HLWeil HLWeil moved this from Ready to In progress in ARCStack Jun 5, 2024
@HLWeil HLWeil added Type: Feature Request This item is confirmed by the maintainers to be a request for a new feature and removed Status: Needs Triage This item is up for investigation. labels Jun 5, 2024
@HLWeil HLWeil self-assigned this Jun 6, 2024
@HLWeil
Copy link
Member Author

HLWeil commented Jun 12, 2024

Moved to Iteration 3, as it seems to be more complex than initially expected.

The central problem is, that the Data Objects appear in several places both in the xlsx(datamodel) and the RO-Crate representation. In RO-Crate cross-references are needed, which should be well thought out. Quick and Dirty solutions will only lead to problems later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature Request This item is confirmed by the maintainers to be a request for a new feature
Projects
Status: In progress
Development

No branches or pull requests

1 participant