Conversation
Contributor
|
An Invenio template could make sense, but for Zenodo I think is better to keep the regular file source which is integrated with the UI. Also, if I get the idea correctly, having a template for Zenodo doesn't provide you with anything extra as a user apart from the extra step to configure it 🤔 |
Member
Author
We discussed this in person. Zenodo and Invenio are not yet ready to be removed / migrated to user-based object stores. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@davelopez do we need an invenio and a zenodo file source template? The Zenodo template could be a URL-hardcoded invenio one, plus a boolean for the sandbox option.
What do you think?
xref: #1396
I think we can at first merge #1396 and then this one a week or two later.