Migrate Issue indexes #31

Closed
opened 2019-08-22 19:57:14 +00:00 by cedewey · 14 comments
cedewey commented 2019-08-22 19:57:14 +00:00 (Migrated from gitlab.com)

Background

Issue indexes are now Collections. They will be migrated over manually.

Work Required

  • @joshua_davis ensure that the structure of Collections will work well - works well but won't ever fit all use cases
  • x @joshua_davis manually move over the Issue index content - will instead migrate automatically as is
## Background Issue indexes are now Collections. They will be migrated over manually. ## Work Required * [x] @joshua_davis ensure that the structure of Collections will work well - works well but won't ever fit all use cases * x @joshua_davis manually move over the Issue index content - will instead migrate automatically as is
mlncn commented 2019-08-30 16:59:36 +00:00 (Migrated from gitlab.com)

mentioned in commit 69ebe9ce26

mentioned in commit 69ebe9ce26458ffc260c22a1132fd4989ec46d2d
mlncn commented 2019-08-30 21:34:27 +00:00 (Migrated from gitlab.com)

The 29 issue indexes are to be manually migrated to new Collection content type after the final migration has been run (ideally, tomorrow).

The 29 issue indexes are to be *manually* migrated to new Collection content type *after* the final migration has been run (ideally, tomorrow).
mlncn commented 2019-08-30 21:34:27 +00:00 (Migrated from gitlab.com)

assigned to @joshua_davis

assigned to @joshua_davis
cedewey commented 2019-08-30 22:05:10 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
mlncn commented 2019-08-31 16:55:37 +00:00 (Migrated from gitlab.com)

marked this issue as related to #19

marked this issue as related to #19
mlncn commented 2019-08-31 17:03:52 +00:00 (Migrated from gitlab.com)

In call today with @joshua_davis and @cedewey we concluded that the simple list of items was not sufficient for more complex collections (where the headers introduce different parts of the list).

Following the Drutopia practice of Paragraphs can fix this; the item references can be in a paragraph instead of directly on the collection, and so can be broken up and interspersed with titles.

In call today with @joshua_davis and @cedewey we concluded that the simple list of items was not sufficient for more complex collections (where the headers introduce different parts of the list). Following the Drutopia practice of Paragraphs can fix this; the item references can be in a paragraph instead of directly on the collection, and so can be broken up and interspersed with titles.
mlncn commented 2019-09-23 15:05:05 +00:00 (Migrated from gitlab.com)

mentioned in issue #13

mentioned in issue #13
mlncn commented 2019-09-30 19:30:00 +00:00 (Migrated from gitlab.com)

We're going to do this automatically instead, because generally the structured content version of collections will not be used.

We're going to do this automatically instead, because generally the structured content version of collections will *not* be used.
mlncn commented 2019-09-30 19:30:11 +00:00 (Migrated from gitlab.com)

assigned to @gnuget and unassigned @cedewey and @joshua_davis

assigned to @gnuget and unassigned @cedewey and @joshua_davis
mlncn commented 2019-09-30 19:30:19 +00:00 (Migrated from gitlab.com)

(i did the first draft of the migration)

(i did the first draft of the migration)
mlncn commented 2019-09-30 19:31:17 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
mlncn commented 2019-09-30 19:31:19 +00:00 (Migrated from gitlab.com)

marked the checklist item @joshua_davis ensure that the structure of Collections will work well - works well but won't ever fit all use cases as completed

marked the checklist item **@joshua_davis ensure that the structure of Collections will work well - works well but won't ever fit all use cases** as completed
cedewey commented 2019-10-16 20:24:51 +00:00 (Migrated from gitlab.com)

All the issues and movement pages are present and look good. Closing!

All the issues and movement pages are present and look good. Closing!
cedewey commented 2019-10-16 20:24:51 +00:00 (Migrated from gitlab.com)

closed

closed
Sign in to join this conversation.
No milestone
No project
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: geo/geo-coop#31
No description provided.