-
Notifications
You must be signed in to change notification settings - Fork 5
Feature: Initiate delete from SHARE #251
Comments
@mcritchlow Our existing working feature "Pushing to OSF staging" seems not working as I tested yesterday. I've emailed to Rick Johnson to ask if there is any change on OSF side that affect it and I am still waiting for his reply. |
@gamontoya The records that i pushed recently doesn't show up in share staging. "id": 12396, And I emailed to Rick Johnson about the above problem but haven't got any response yet. |
@hweng What are you trying to do? Push records to Share and then delete them? |
@hweng Also, how long ago did you contact Rick? Did you do it via email? |
@gamontoya Could you try to push a record from dams4 staging: http://librarytest.ucsd.edu/dc/ and see if you can find it from share staging now? This feature has been working well for quite a while in dams4, and we tested it was working after OSF updated their API in October but recently it has not been working for me. |
@hweng Okay, I just pushed one now. |
@hweng What is the URL to check the push? |
@gamontoya The message just means it is successfully pushed out to OSF staging sever. But if OSF side doesn't show it up on their UI for some reason, we have no way to control how their application behavior. |
To keep track - A email from Rick: Chris Seto: "Ah, chances are its just staging being wonky. The task queue generally gets bloated because staging is trying to keep up with a production load of data even though it has less than half the size. When I get some time and finish up the bug I've been working on, I'm going to clear all the data and only enable the most recent harvesters." I will check in with him later to see if there is a status update, but hopefully they will show up sometime later today. Thanks! |
Per talking with SHARE team, they have been still working on queue issues on staging environment. |
@mcritchlow From the documentation for SHARE API V2, the deletions is not yet supported: A question about "is the deletion supported by SHARE v2" was sent to Lauren Barker on Wednesday and I'm still waiting for her response. |
Got “OSF | Page not found” issue when test pushing a record to OSF staging with API V2. I've sent a message to OSF developers for the issue and still wait for their response. |
This work is "On hold" now as I was informed. |
Please add the ability to initiate a deletion request via the SHARE Notify service for a give record.
This can be in the form of a new link that is only accessible to the group that is able to create SHARE records for Collections.
Testing/QA Group: @gamontoya @hjsyoo
The text was updated successfully, but these errors were encountered: