Islandora 7/8 feature parity tracking list

[bondjimbond]

Requesting an easy-to-find document, updated with each release, covering Islandora 8 development in terms of which Islandora 7 features are currently supported, in development, or deprecated/not going to happen.

Discussion in Slack: https://islandora.slack.com/archives/CM5PPAV28/p1626794806415700

This would be useful for any site looking at migrating, and might help identify the elements holding folks back from migrating. It would be a helpful guide for development.

@Islandora/documentation is this something the DIG would be interested in?

[nigelgbanks]

Reference material: https://islandora.ca/content/islandora-8-fact-sheet

[mjordan]

2021-07-21 Tech Call: I will start a Google Doc listing all the 7.x core modules, Community is invited to start listing functionality.

[mjordan]

Islandora 7.x to Islandora 2 functionality map

[amyrb]

Does it make sense to put aspects of functionality that are more related to the site interface/theme/configuration rather than the content modules in another sheet in the Google doc that Mark linked above? A possible catch is, I'm not sure how generalizable those things were in i7. For instance, our i7 site used the Carapace theme, and we were able to do things like specify by collection which facets to show for different collections, search from the top search box within individual collections, there was a field in the collection metadata to put a link to a finding aid, etc. I don't know if that was standard across any variation of i7 independent of theme, although I suspect it was linked to how collections were handled in i7, which is different in i8.

[rosiel]

Totally valid - there's a section at the bottom for "extensions"

[kstapelfeldt]

When I went looking into this today to see if I could make tickets for things that are described in this document, I wondered if we have user stories for all these features. I wrote something as a sample in 24 H for Access Control (Hopefully not overstepping)

I think a format like this might help us describe what it is we want the software to be able to do for people by default, and how things will be accomplished in such a different framework. If folks agree, then I think that might be a way forward that helps us organize and make more accessible this list, particularly to those greenfield users who may not understand what is meant by "audit datastream" for example.