forked from CenterForOpenScience/osf.io
-
Notifications
You must be signed in to change notification settings - Fork 0
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
test #189
Merged
Johnetordoff
merged 54 commits into
Johnetordoff:develop
from
CenterForOpenScience:develop
Aug 30, 2023
Merged
test #189
Johnetordoff
merged 54 commits into
Johnetordoff:develop
from
CenterForOpenScience:develop
Aug 30, 2023
Conversation
This file contains 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
* redirect rr to workflow and remove dead code. * consolidate routes and remove superfluous function --------- Co-authored-by: John Tordoff <>
* Registration email updates for GFS Admins * Update sign-off for admin emails
* Allow s3 to use subfolders as the root folder of a files addon * use colon delineation for s3 buckets, remove bucket_name query_param * fix issue with over mocking Gitlab messing with serializer method * revert serializer for correct id * de-ordinaryize the s3 calling format this allows non us-east-1 regions to work for s3 * add migration for s3 folder_ids and names * change migration to management command * fix tests for management command * flake8 fixes * reintroduce OrdinaryCallingFormat and remove from get_bucket * make migration allow for already converted folder_ids and folder_names * make get bucket names use the correct calling format * clean-up and revert old changes * use boto3 to access bucket regions using V4 s3 auth * move add delim command to management command dir for s3 improvment --------- Co-authored-by: John Tordoff <> Co-authored-by: John Tordoff <[email protected]>
* OSFMAP Search Improvements (#10386) * [ENG-4618] User Search metadata (#10428) * [fixes] Search Improvement tests (#10432) * Fix Search Improvement test (#10435) * [Fix] Filterable "resourceNature" (#10434) * Add Withdrawal metadata to SHARE (#10430) * [ENG-4617] Send File Metadata to SHARE (#10436) * Fix: Skip sending non-provider collections to SHARE (#10439) * Optimize recatalog_metadata via celery (#10440) * fix: send utf-8 to shtrove (#10437) * [fix] Search/Metadata back-compat and fixes (#10443) * [fix] Add missing registration component metadata (#10444) * d42708e
- fix: archivedAt in metadata should be uri-ref - fix: correct "academia" social link in metadata - fix: ignore bad-smelling identifiers when serializing for datacite
if a custom subject has the exact name of its bepress synonym, do not bother including both in metadata records (they result in wrong-looking duplicates in the search interface and add no value to the metadata)
- handle FileVersion with null creator - do not index osfstorage file without versions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
Changes
QA Notes
Please make verification statements inspired by your code and what your code touches.
What are the areas of risk?
Any concerns/considerations/questions that development raised?
Documentation
Side Effects
Ticket