agaric/agaric-coop
10
1
Fork 0
Code Issues 102 Pull requests Projects Releases Packages Wiki Activity

Decide which content types to apply services and technologies vocabularies to. #88

New issue
Closed
opened 2018-10-02 17:59:17 +00:00 by cedewey · 15 comments
cedewey commented 2018-10-02 17:59:17 +00:00 (Migrated from gitlab.com)
Copy link

Related Issue #94

Right now Services and Technologies have a term reference field on the Case Study content type.

We need to decide if and which other content types to apply those to and then create the correct module(s) to make it happen.

Work Required

  • Decide which (if any) content types Services vocab will apply to
  • Decide which (if any) content types Technologies vocab will apply to
  • Implement Services vocab and fields as appropriate
  • Implement Technologies vocab and fields as appropriate
Related Issue #94 Right now Services and Technologies have a term reference field on the Case Study content type. We need to decide if and which other content types to apply those to and then create the correct module(s) to make it happen. ## Work Required * [x] Decide which (if any) content types Services vocab will apply to * [x] Decide which (if any) content types Technologies vocab will apply to * [x] Implement Services vocab and fields as appropriate * [x] Implement Technologies vocab and fields as appropriate
cedewey commented 2018-10-02 18:00:42 +00:00 (Migrated from gitlab.com)
Copy link

I think Services and Technologies should both apply to Blog Posts and Initatives. If we end up creating a Service content type then they could both be applied there too.

I think Services and Technologies should both apply to Blog Posts and Initatives. If we end up creating a Service content type then they could both be applied there too.
mlncn commented 2018-10-12 05:51:39 +00:00 (Migrated from gitlab.com)
Copy link

@cedewey agreed. And we're not using content types Article or Resource?

@cedewey agreed. And we're not using content types Article or Resource?
mlncn commented 2018-10-12 05:52:00 +00:00 (Migrated from gitlab.com)
Copy link

unassigned @mlncn and @cedewey

unassigned @mlncn and @cedewey
cedewey commented 2018-10-12 18:35:58 +00:00 (Migrated from gitlab.com)
Copy link

Correct

Correct
cedewey commented 2018-10-16 16:00:02 +00:00 (Migrated from gitlab.com)
Copy link

@mlncn that's right, at least for now we're not using Article or Resource.

Do you know I would go about that? The only examples of cross-cutting taxonomies are Tags and Topics, which are added in drutopia_core. Services and Technologies, however, aren't vocabs that most Drutopia sites will use.

@mlncn that's right, at least for now we're not using Article or Resource. Do you know I would go about that? The only examples of cross-cutting taxonomies are Tags and Topics, which are added in drutopia_core. Services and Technologies, however, aren't vocabs that most Drutopia sites will use.
cedewey commented 2018-10-16 16:00:08 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @mlncn and unassigned @gnuget

assigned to @mlncn and unassigned @gnuget
cedewey commented 2018-10-16 18:08:31 +00:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
mlncn commented 2018-10-16 19:13:03 +00:00 (Migrated from gitlab.com)
Copy link

Discussed in IRC, and as 'drutopia_case_study' will be treated as a custom module for now, the additional vocabularies and fields will be added directly to it.

Discussed in IRC, and as 'drutopia_case_study' will be treated as a custom module for now, the additional vocabularies and fields will be added directly to it.
cedewey commented 2018-10-16 20:57:37 +00:00 (Migrated from gitlab.com)
Copy link

marked the checklist item Decide which (if any) content types Services vocab will apply to as completed

marked the checklist item **Decide which (if any) content types Services vocab will apply to** as completed
cedewey commented 2018-10-16 20:57:37 +00:00 (Migrated from gitlab.com)
Copy link

marked the checklist item Decide which (if any) content types Technologies vocab will apply to as completed

marked the checklist item **Decide which (if any) content types Technologies vocab will apply to** as completed
cedewey commented 2018-10-16 20:57:39 +00:00 (Migrated from gitlab.com)
Copy link

marked the checklist item Implement Services vocab and fields as appropriate as completed

marked the checklist item **Implement Services vocab and fields as appropriate** as completed
cedewey commented 2018-10-16 20:57:40 +00:00 (Migrated from gitlab.com)
Copy link

marked the checklist item Implement Technologies vocab and fields as appropriate as completed

marked the checklist item **Implement Technologies vocab and fields as appropriate** as completed
cedewey commented 2018-10-16 21:00:37 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in merge request !22

mentioned in merge request !22
mlncn commented 2018-10-16 21:26:47 +00:00 (Migrated from gitlab.com)
Copy link

closed via merge request !22

closed via merge request !22
mlncn commented 2018-10-16 21:26:47 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 623c47aadf

mentioned in commit 623c47aadf312258326fd4b2ccec7950d2c46a91
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
bbb-test
D9-upgrade
drush-9-aliases
provision-dewey
No results found.
Labels
Clear labels   
A11y

Accessibility-related issues

  
Automated Testing

   
Contributable

Issues with work that can (potentially) be contributed back to Drupal or other FLOSS projects.

  
Contributed

Tag issues where we have contributed work back to FLOSS projects (replace Contributable tag; the Contributed tag can be removed once the contribution is recorded in a blog or something.

  
Decision

An issue that requires a decision be made.

  
Design

Issues that should include a UX/design work or review.

  
Development

   
Drutopia

Issues related to Drutopia features or infrastructure, or are potential Drutopia enhancements (with tag Contributable).

  
Feature Request

   
IndieWeb

Anything related to interlinking web sites in a broadly IndieWeb fashion, see https://indieweb.org/

  
Infrastructure

   
Marketing

   
Needs documentation

When an issue has uncovered something that should be documented in a user guide or the project wiki or anywhere else outside the issue queue.

  
status::Abandoned

An issue that has been abandoned and will not be completed.

  
status::Blocked

An issue that is blocked for a reason outside Agaric's control.

  
status::Deploy

An issue that has been tested and is ready to be deployed.

  
status::Doing

   
status::Done

   
status::In Review

An issue that has been completed and is ready for a code and/or design review.

  
status::Needs Clarification

   
status::Test

An issue that has been completed and is ready to be tested.

  
status::To Do

An issue that is an agreed priority and has all information needed to be completed.

  
type::Bug

   
type::Task

   
type::User Story
No labels
A11y
Automated Testing
Contributable
Contributed
Decision
Design
Development
Drutopia
Feature Request
IndieWeb
Infrastructure
Marketing
Needs documentation
status::Abandoned
status::Blocked
status::Deploy
status::Doing
status::Done
status::In Review
status::Needs Clarification
status::Test
status::To Do
type::Bug
type::Task
type::User Story
Milestone
Clear milestone
No items
No milestone
Sprint 1
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: agaric/agaric-coop#88
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?