Hi!

I was able to understand how this issue works. I confess I was a bit
lost on the subject. Now, I need to understand, for example how CCL
inserts into the repository. For example, here in our authorization
term has a part that says: I authorize the Library System of the
Federal University of Rondônia to make available
the work in the Institutional Repository free of charge, according to
the public license Creative
Commons License 4.0 International by me declared under the following
conditions. If there is
publisher's interest and have the options:
Do you allow commercial use of your work?
( ) Yes No
Allow changes to your work?
( ) yea
() yes counting others share for the same license
( ) not
The work remains protected by Copyright and / or other applicable
laws. Any use of the
work other than that authorized under this license or by copyright law
is prohibited.

But in the repository for all publications only the message appears:
Items in the repository are protected by copyright, with all rights
reserved, except where indicated otherwise.

Forgive me, I am now entering this universe and trying to understand
how it works.
This discourse is being of great value.


Em qui, 29 de nov de 2018 às 18:24, Fitchett, Deborah <
[email protected]> escreveu:

> Another not-lawyer here. J
>
>
>
> Essentially, the person who owns the copyright (usually but not always the
> author) has the right to determine whether, how, and by whom copies of the
> work (either print or electronic) can be made.
>
>
>
> If the copyright holder gives someone permission to make copies, that’s
> called a license. Eg for something to be put on a repository, the copyright
> holder has to grant permission (ie a license) to the repository to make a
> copy. If they’re only granting permission to the repository and not to
> anyone else then it’s appropriate to display “all rights reserved”.
>
>
>
> But the copyright holder can choose to grant other licenses, like a
> Creative Commons license. If they did that, they should display the CC
> license information instead of “all rights reserved” because they’re no
> longer reserving all rights – they’re granting some rights, and reserving
> some rights, and these are described by the CC license.
>
>
>
> It’s always easy for a copyright holder to grant new permissions – so if
> something you own is “all rights reserved” you can change that to a CC
> license. But it’s harder to take away permissions, so if it already has a
> CC license it would be difficult or maybe impossible to change it back to
> “all rights reserved”.
>
>
>
> (More information about Creative Commons licenses is at
> https://creativecommons.org/licenses/ - the bottom of the page links to
> translations in other languages.)
>
>
>
> Deborah
>
>
>
> *From:* [email protected] <
> [email protected]> *On Behalf Of *Joseph Frank Rogani
> *Sent:* Friday, 30 November 2018 4:54 AM
> *To:* [email protected]
> *Cc:* [email protected]; [email protected]
> *Subject:* Re: [dspace-community] licences and copyright
>
>
>
> Hello again,
>
> I am not a lawyer either, but I agree there is a contradiction.
>
>
>
> It also depends on what kind of document you are depositing: if it is a
> Ph.D., say, unless it has embargoes or patent restrictions, it should be
> open, though respecting citations in case of use. What I actually meant is
> that Abdulrahman should go for a CCL, leaving the author free to decide (is
> he the author?) which permissions to give for the use of the item.
>
> I don't know if you agree on this.
>
>
>
> Kind regards
>
> Joseph
>
>
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/dspace-community.
> For more options, visit https://groups.google.com/d/optout.
>
> ------------------------------
>
> "The contents of this e-mail (including any attachments) may be
> confidential and/or subject to copyright. Any unauthorised use,
> distribution, or copying of the contents is expressly prohibited. If you
> have received this e-mail in error, please advise the sender by return
> e-mail or telephone and then delete this e-mail together with all
> attachments from your system."
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/dspace-community.
> For more options, visit https://groups.google.com/d/optout.
>


-- 


*Edoneia Sampaio** Miranda*

*Bibliotecária Documentalista *
*Fundação Universidade Federal de Rondônia*
*Tel.: (69) 2182-2164*

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

Reply via email to