Configuring Claimed Copyrights

Configuring Claimed Copyrights

Summary

This articles discusses how to configure claimed copyrights.

Synopsis

Claimed copyright settings can be used to have Palamida designate a selection of copyrights to be ignored when the software scans for third-party indicators. Only "unparseable" copyrights can be ignored. An unparseable copyright is one that is not strong enough to match a pattern but still appears to be copyright statement.

Files containing copyrights put into the "claimed bucket" will not be flagged for third-party indicators if the customer's claimed copyright is the only indicator.This behavior ensures that real copyright matches are still detected. Ignored copyrights are not accessible in the scan results. (For more information on how to control the sensitivity of copyright detection, please refer to the section, "Tuning Copyright Detection" in the Enterprise Installation and System Administration Guide.)

Discussion

Edit the file $palamida/config/scanEngine/claimedCopyrights.txt

##############################################################################
# This file may be used to force detected copyrights into the -claimed- bucket.
# The purpose of this is to move all copyrights that belong to the user into a
# separate bucket (-claimed-) so that they do not cause the scanned file to be
# flagged as having third-party indicators if the only evidence is the customer's
# copyright.
##############################################################################

##############################################################################
# The case-sensitive strings or regular expression patterns below will cause a
# detected copyright to be moved into the -claimed- bucket.
##############################################################################
#[P|p]alamida

Defining copyright patterns for which to take ownership and move to the -claimed- bucket:

  • Do not use commas (,) while defining copyright, date or owner patterns. Since commas are used as delimiters, they will end up tokenizing your patterns into multiple values. For example: Palamida, Inc. should be defined as Palamida Inc. (Note that there is no comma in the owner pattern.)
  • Do not use any of the following reserved characters: \n \r | # ! % : ; , / * " space. If you use these reserved characters, they will be replaced by a whitespace (' ') character.
  • If Java special characters are part of the defined copyright pattern, ensure that double slashes are used to escape both the properties file parsing as well as the Java interpretation. An example of this is Copyright 2008 would be defined as Copyright \[C\] 2008.
Labels (1)
Was this article helpful? Yes No
No ratings
Comments

How would you create the Custom Copyright and Claimed Copyright on v7?

There are two table entries in mysql database with the following names:

"PSE_CUSTOM_COPYRIGHT" and "PSE_CLAIMED_COPYRIGHT" but they are empty.

Could you provide some examples for v7?

 

Thank you,

Hello,

Is it possible to claim copyrights like this with the latest 2021 R2 version? or is it a regression in functionalities?

Thanks,

Christophe.

Version history
Revision #:
1 of 1
Last update:
‎Nov 15, 2018 05:12 PM
Updated by: