Custom Query (2152 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (463 - 465 of 2152)

Ticket Resolution Summary Owner Reporter
#2255 fixed Organizations (Privacy + Ownership) ross ross

Reported by ross, 2 years ago.

Description

[x] The publisher_form extension and the 'publisher' component of the system will be renamed to organizations to both make its functionality clear, and to differentiate it from the publish auth profile.

Ownership of datasets is important and this ticket will enforce membership for a dataset to a single individual organization. The workflow for adding a dataset to a publisher/organization will stay the same but there will be no mechanism for adding existing datasets to an organization from within the organization forms.

[x] New datasets can be created from the organization form, in which case the organization will be set in the dataset form dropdown (with privacy set to private - see below)

[x] Datasets created from direct access to /dataset/new will have a drop down showing all of the organizations available to the current user.

[x] When editing a dataset the organization can only be changed if the current user is the admin of the current organization, and only then to one of the organizations available to the current user.

Only Organization admin can see the edit Organization form.

[x] Privacy will be enforced by changing the dataset form to have a public/private switch next to the organization drop-down which will be set as the capacity with which the dataset is added to an Organization. Private means visible only within the Organization, and should be the default.

[x] Search will be affected as the public/private status of a dataset will need to be added to the schema

[x] Only public datasets showing in site search, and private showing in organization dataset search (if user is within the organization).

[x] Make sure resources are restricted in visibility if the parent dataset is private

[x] Documentation should be updated to reflect these changes.

[x] Verify, then add, then re-add to documentation.

  • A User joins or creates an Organization
  • If creator of the Organization User becomes administrator of the Organization otherwise they become a Member.
  • Creation of new Organization must be approved by a System Administrator
  • New Members must be approved by the Organization Administrator
#2254 fixed better hooks for templates toby toby

Reported by toby, 2 years ago.

Description

TD look at issues and then email ckan-dev

meeting notes from 21-3-2012 general ideas non specific

Problem:

  • We want to remove the Transformer usage due to performance and its close tie to genshi
  • Want a standard way for core code and extensions to put code into the templates where *templates request it* (templates control insertion rather than extensions ...)
  • Stacking versus overwriting on entry points

Options:

  • placeholders or helper methods
  • {{user _info}} {{sub_menu}} is this equivalent to <span class="insert-user-info"></span>
    • [xyz arguments] -> h.load_snippet('xyz', ...)
  • ${h.snipit()}
#2253 wontfix CMAP [super] toby toby

Reported by toby, 2 years ago.

Description

Somewhere for CMAP stuff not in other tickets

need to create some general tickets

  • template changes
  • general demo server setup
Note: See TracQuery for help on using queries.