Opened 10 years ago

Last modified 9 years ago

#3531 new enhancement

After creative commons liblicense (licensing integration) add search by license capability

Reported by: rejon Owned by: Eben
Priority: normal Milestone: Future Release
Component: journal-activity Version:
Keywords: Cc: asheesh@…, sj@…
Blocked By: #3529 Blocking:
Deployments affected: Action Needed: never set
Verified: no


The summary speaks for itself. It should be easy to search by license to find useful content.

Change History (11)

comment:1 Changed 10 years ago by jg

  • Milestone changed from Untriaged to V1.1

This is after feature freeze for our first release: I'm targeting for our V1.1 release.

comment:2 Changed 10 years ago by tomeu

  • Owner changed from tomeu to Eben

Eben, can you spec this feature?

comment:3 Changed 10 years ago by Eben

I don't yet have any information about how licensing is being integrated into the Journal. We don't really have room for an additional filter at this point. Perhaps if the licensing info was stored as a tag, it would fall neatly into place when we add sorting functionality, so that you could filter by image type and sort by license type to see, for instance, all of the images of a particular license type grouped together.

Can someone give me more info on how this is being integrated?

comment:4 Changed 9 years ago by ixo

What's the latest status on licensing integration? Looks like it may have fallen through the version cracks. :)

comment:5 Changed 9 years ago by rejon

IXO, yes, it seems so. We need to get this into update 2 and get it in now so it can be adequately tested.

Alright, the target is to get these into update 2...marco, tomeu, sj, jg, can you update this one so that it can be on track for update 2 due in 2-3 months...

comment:6 Changed 9 years ago by rejon

  • Milestone changed from Future Release to 8.2.0 (was Update.2)

I'm hopeful that we can get this into the next release. Liblicense is now in rawhide RPM repo and ready to allow for testing of this. Please advise if more info is necessary to make this functionality visible, etc.

We are eager to publicize this and gear up support.

comment:7 Changed 9 years ago by rejon

  • Milestone changed from 8.2.0 (was Update.2) to Future Release

Oops, changing this one to future release because we have not planned to be adding this functionality if you guys are not interested in it...we are still just trying to get our basic features through we discussed ages ago.

comment:8 Changed 9 years ago by marco

Where are the patches? Also I don't see any answers to Eben question in comment 3.

You should follow the review process if you want to get something into the journal:

We are in feature freeze since yesterday, so it's tricky now. But let's see the code and then we can decide when to land it.

comment:9 follow-up: Changed 9 years ago by rejon

Eben, please excuse me, but it is quite hard to keep track of all the changes in procedures, etc, in order to add our functionality.

I appreciate you working with us on this.

As I said above, I changed this back to a future release I think before you hit save on your comment. There is older code to add licensing functionality to the journal before some newer functionality which is at this item:

Would you prefer it done the way described in this feature request or at item 3529?

comment:10 in reply to: ↑ 9 Changed 9 years ago by marco

Replying to rejon:

Would you prefer it done the way described in this feature request or at item 3529?

I'm confused. It seem like 3529 is a pre requisite for this ticket and not an alternative. Am I misunderstanding?

comment:11 Changed 9 years ago by rejon

  • Action Needed set to never set
  • Blocked By 3529 added

Yes, agree, is prerequisite for this enhancement.

Note: See TracTickets for help on using tickets.