-
Notifications
You must be signed in to change notification settings - Fork 490
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
3353 batch job import #3497
3353 batch job import #3497
Conversation
…in favor of system properties
…tions to admin in all cases
…blished dataset tests
…y truncated, json
… the writer class
…test; misc. cleanup
… IpAddress; removes catching EJBException
…o override checksumType and checksumManifest; API returns NOT_IMPLEMENTED error if mode isn't MERGE; adds a dataset lock during import; adds integration test for DataverseRole.EDITOR
… no subdirectory, should be empty)
… a detailed log file (in addition to json)
…dle both the "package file" imports, and imports of files as individual datafiles, as was originally developed.
…ticket) agreed upon during the last code review).
OK, we agreed to make a number of changes during the last code review, 5 total, addressed in my latest commit:
Please review and see if anything's missing. Also, Phil just found something else that I missed - Bill created some RestAssured tests that are failing, now that the import process has been changed. Let's discuss how to proceed; should we move it to QA and treat the RA tests as a separate issue? Or fix it now? Also, the branch needs to be synced up to the develop, before it can be QAed. |
Resolved Conflicts: src/main/java/edu/harvard/iq/dataverse/authorization/providers/builtin/DataverseUserPage.java
fixes the "multiple passes problem" - size, etc. per the final conversation with Pete: a new parameter - "uploadFolder"; the manifest goes back to specifying the files by the relative path inside the upload folder; the manifest should be placed inside the upload folder.
RFI Checklist
Before submitting the pull request, fill out sections (1.) Related Issues and (2.) Pull Request Checklist.
1. Related Issues
List and link to the issues in this Pull Request.
2. Pull Request Checklist
3. Review Checklist
After the pull request has been submitted, fill out this section.