PubMan Func Spec Copyright

This page serves  an overview on the requirements for an institutional repository regarding rights (usage rights, licenses etc.)

PLEASE NOTE...WORK IN PROGRESS

=UC_PM Type of full text=

'''Status: implemented '''

Following content categories are available for each uploaded full text (see also File properties) and are selected by the user when submitting the file:
 * pre-print: Pre-peer-review version of an article that is to be submitted for peer-reviewed publication (i.e. Stage 1, manuscript)
 * post-print: The postprint is the creator's peer-reviewed final draft, accepted for publication (i.e. Stage 2, reviewed manuscript with changes)
 * publisher version: The published version of the article. Regarding the content, the publisher version is identical to the post-print. (i.e. Stage 3)
 * any fulltext: full text which won't be submitted for peer-review or stage/version not known.
 * abstract: Provides only the summary of the article.
 * table of contents: The overview of the article content
 * supplementary material
 * copyright transfer agreement
 * correspondence

=UC_PM_CR_01 Provide Rights= When a user uploads/saves components (i.e. full text) and/or locaters, he/she can provide appropriate rights information on uploaded content.

Status / Schedule
Status: in specification

Schedule: R 5

Actors
Depositor Moderator

Flow of Events

 * the user starts easy or full submission
 * the user gives basic information of the item
 * he/she decides to upload a file/to save a file locater
 * after uploading/saving the respective file/URL the user chooses type and description of the content
 * the user chooses the visibility of the attached file:
 * public or restricted (NOTE: for locaters visibility is always public!)
 * if the choice is restricted, he/she chooses between private or audience
 * for restricted files the user has the option to provide info on embargo date
 * independently of visibility the user has the option to provide a CC License
 * DC term: license document
 * CC-license type per component
 * optionally
 * controlled vocabulary
 * internationalized
 * optionally the user can provide a rights statement
 * DC term:rights statement
 * per component
 * the user has the possibility to fill in a rights statement
 * this field is optional and contains free text
 * optionally the user has the possibility to provide a copyright date
 * DC term: date copyrighted
 * per component
 * the user has the possibility to fill in a copyright date
 * this field is optional and has usual date format (YYYY-MM-DD -> but it's possible for the user just to state a year)
 * before the item is submitted/released a information message shows up: "You are going to submit/release an item with rights information. Please be aware that you have checked these information!"
 * these information message shows up only if the user provides rights information for the submitted item and its component(s)
 * the item is submitted/released
 * the use case ends successfully

Post-Conditions / Results

 * the item is submitted/released with respective right information

Constraints
none - for files as well as for locaters

Related Usecases

 * UC_PM_SM_12_file_upload
 * UC_PM_SM_04_fetch_metadata_from_external_system
 * UC_PM_EASM_02_fetch_full_text_by_identifier
 * UC_PM_QA_08_release_item
 * UC_PM_SM_02_edit_item
 * UC_PM_SM_03_submit_item

Future development

 * simple workflow for R5 - has to be developed within the copyright handling project
 * in future maybe integration of further license types - for R5 implementation to provide a CC License

=UC_PM_CR_02 Provide embargo date= Some publishers allow - depending on their policy - to publish the publisher's version after certain time in any other repository. To be able to align the access level of full texts in the repository with the respective embargo time defined in the publisher's policy, embargo times of journals have to be tracked.

Status / Schedule
Status: in specification

Schedule: R 5

Actors
Depositor Moderator

Flow of Events

 * in case that the user chooses visibility restricted, for both restrictions (audience and private) it's possible to provide a date which informs about the end of the embargo time
 * it's an optionally field
 * the field has usual date format (YYYY-MM-DD -> but it's possible for the user just to state a year)


 * the user adds an embargo date
 * the embargo date is saved
 * the use case ends successfully
 * NOTE:due to legal insecurity no auto-release of item versions with expired embargo date
 * NOTE: in case of file visibility is set to "public", because the embargo date is expired, embargo date is not visible any more in detailed item view

Post-Conditions / Results

 * an embargo date is provided for a restricted component

Constraints

 * only for restricted components

Related Usecases

 * File Visibility

Future development

 * option a): provide the possibility to look-up embargo dates in Sherpa/Romeo (Japanese version)
 * option b): the user can select from autosuggest-journal list the respective journal, the embargo dates defined for this journal are pre-filled (might not be feasible, as it's only possible/useful, if we have reliable data on embargo times per journal -> see also discussion on rights metadata for journals under control of named entities

=UC_PM_CR_03 Provide CC License= During submission the user has the possibility to provide a CC License for the uploaded file/locater.

Status / Schedule
Status: in specification

Schedule: R 5

Actors
Depositor Moderator

Flow of Events

 * independently of visibility the user has the option to provide a CC License
 * DC term: license document
 * CC-license type per component
 * optionally field
 * controlled vocabulary
 * there are six CC License options:
 * Attribution
 * Attribution-Noncommercial
 * Attribution-Noncommercial-No Derivative
 * Attribution-Noncommercial-Share Alike
 * Attribution-No Derivative Works
 * Attribution-Share Alike


 * these six options are displayed with the respective icons (controlled vocabulary; might be handled by control of named entity service)
 * the icons are linked to the written type of CC License -> possibility for the user to get detailed information about the chosen license type
 * license has to be internationalized -> Creative Commons International
 * the user can select type and international variant (i.e. implicitly the current version) -> this info is stored together with the item
 * for R5, we will not store license content in escidoc
 * license information are saved
 * the use case ends successfully

Post-Conditions / Results

 * a selected type of CC License is provided for the component

Constraints
none - for files as well as for locators

Future development

 * nice to have: default CC-license type
 * if possible to define default on content level:
 * a) no CC-type at all
 * b) set default

=UC_PM_CR_04 Modify Rights= The user wants to modify the rights information of a component/locater.

Status / Schedule
Status: in specification

Schedule: R 5

Actors
Depositor Moderator

Flow of Events

 * rights statement, date copyrighted and license document can be modified after they have been submitted; for released items it depends on workflow
 * if the user wants to change rights information -> he/she edits/modifies the respective metadata of an item
 * rights statement: free text; simple modification possible
 * date copyrighted: date format; simple modification possible
 * license document: selected document -> license might change over time -> needs possibility to change the license type or de-select license (no license any more)
 * changed metadata are saved
 * the use case ends successfully
 * NOTE: in case of file visibility is set to "public", because the embargo date is expired, embargo date is not visible any more in detailed item view

Post-Conditions / Results

 * rights information are modified

Constraints
none - for pending and submitted items as well as for released items (no problem regarding citation because of versioning)

Related Usecases

 * UC_PM_QA_11_modify_item

Future development
=UC_PM_CR_05 View Rights= The user wants to view the rights information af an item.

Status / Schedule
Status: in specification

Schedule: R 5

Actors
all users

Flow of Events
Detailed Item View
 * rights statement, date copyrighted and license document are metadata fields which are displayed on detailed item view page
 * the user selects an item for detailed view
 * rights statement is displayed as free text
 * date copyrighted is displayed as date
 * license document should be displayed as the respective CC license icon (links to written license) together with file name
 * the use case ends successfully

Post-Conditions / Results

 * rights information are displayed on detailed item view page

Constraints
no sorting and filtering for rights information in R5

Related Usecases

 * UC_PM_BD_04_view_item_version

Future development
improvement of filtering and sorting on My Item Workspace/Moderator Workspace
 * for visibility
 * public
 * restricted
 * restricted - audience (with or without embargo)
 * restricted - private (with or without embargo)
 * for embargoed components
 * within embargoed components:
 * all components for which embargo is already over
 * all components for which embargo is soon over
 * for license document (CC license types)

=UC_PM_CR_06 Search for rights information= The user wants to search for selected rights information.

Status / Schedule
Status: in specification

Schedule: R 5

Actors
all users

Flow of Events

 * the user wants to search for selected rights information
 * advanced search should be possible by
 * license document (CC types)
 * visibility:
 * 1. public files (already implemented)
 * 2. restricted files (already implemented)
 * 2.1 private files
 * 2.2 audience files
 * 2.3 embargoed files


 * the use case ends successfully

Post-Conditions / Results

 * the desired query for selected rights information achieves success

Constraints

 * needs update of indexing

Related Usecases

 * PubMan Indexing
 * UC_PM_SR_03_Do_advanced_search

Future development
=Future enhancements=

Automatic creation of PDF-coverpage

 * Context setting, if automatic modification of uploaded PDF
 * add PID and CC-license attached to file
 * Restrict to certain content categories and/or MIME types?
 * see also Requirement NIMS

Workflow for Copyright handling
Aim: Balancing - Keep it simple to facilitate OA publishing, but define necessary restrictions to reduce risk of right infringement for user and MPG

Aspects

 * Legal requirements from MPS as hosting organisation
 * what needs to be documented digitally/physically by whom?
 * Which information needs to be provided in which form at which point in time? (Fürsorgepflicht, Sorgfaltspflicht)


 * Conceptual workflow to integrate various checks for clarifying rights situation
 * cover complete publication workflow (i.e. before actual publication until post-publisher time)
 * cover user interactions with repository: login - deposit - access - re-use (download, export etc.)


 * Focus on "reduce risk of copyright infringement"
 * documented processes (Handreichungen) for deposit and access management, to gain trust

Scenarios

 * original copyright transfer agreement (CTA) is available and checked by librarian
 * original CTA is not available, but journal/publisher has specific agreement with MPS
 * original CTA is not available and information on copyright policies has to be checked by external source (e.g. Sherpa/romeo http://www.sherpa.ac.uk/romeo/api.html)
 * Support OA gold
 * faciliate awareness on MPG OA gold during submission?
 * Define "embargo" time applied by MPG ("Schutzfrist"). Is optional. (why embargo? until when? Freetext) (Example Sengbusch)
 * Can you precise here? Do not understand what is meant--Ulla 09:05, 28 August 2009 (UTC)


 * Documentation/description of Status copyright transfer to MPG for re-use, dissemination, publishing of IP works, e.g. verbal or written copyright transfer to MPG(unknown, verbal, written, contract archived) - => documentation is outcome of final copyright handling workflow. Conclusive action can also provide a transfer, e.g. email saying "Please publish via eDoc").
 * Depends on legal requirements from MPS. In addition, I think, there will be a difference between documentation as substantial part of repository item (needed for LTA, for Export, for re-use) and mere MPG-internal, "administrative" metadata related to the repository item.--Ulla 09:05, 28 August 2009 (UTC)

Related Links
Karla Hahn: Achieving the Full Potential of Repository Deposit Policies. Research Library Issues: A Bimonthly Report from ARL, CNI, and SPARC, no. 263 (April 2009): 24–32 PDF

OA statistics
Status: in specification

Schedule: unclear

see under OA Statistics