-
Notifications
You must be signed in to change notification settings - Fork 58
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
require email address for publication contact #1622
Conversation
* @param integer $aid | ||
* @return void | ||
*/ | ||
public function saveItem($manifest, $blockId, $pub, $actor = 0, $elementId = 0, $aid = 0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When/Where does saveItem() get called, I don't see anything in this PR using it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Contact Jerry to get a reply on this if he doesn't get back on his own.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Nick, saveItem() is called when clicking the "save" button on author editing form. Below is the specific call stack.
- saveDraft() in /plugins/projects/publications/publication.php is called, where "saveitem" task is processed and "saveItem" of curation model is called as $pub->_curationModel->saveItem($this->_uid, $element).
- In saveItem function of curation model, blocks model and its saveItem() is called.
$blocksModel = new Blocks($this->_db);
$blocksModel->saveItem($this->_blockname, $this->_block, $this->_blockorder, $this->_pub, $actor, $elementId); - In saveItem function of blocks model, the saveItem function in the model in models/blocks/review.php is called by code snippet below.
$block = $this->loadBlock($name);
$block->saveItem($manifest, $blockId, $pub, $actor, $elementId);
Co-authored-by: nkissebe <nkisseberth@ucsd.edu>
We want the publication contact have valid email address so that we can reach out to the right person when dealing with the datasets that have been published for over 10 years. Please refer to ticket: https://purr.purdue.edu/support/ticket/2456 where a specification document is attached, as well as a gif about how the function works. The changes have been tested in local development environment.