[Oslc-communications] Site Data Retention and Migration

Wed May 10 08:48:21 EDT 2017

Thanks Mark, this is a great starting list. Once I get access to the site, I’ll evaluate what makes sense to do now and what should wait for the new site. In general, for data migration I think I’ll just have to go through the site section by section when the time comes, and make proposals on what to bring over.

Question: In #6 you mention “strategy proposal for accelerating OSLC standards and adoption”. Is this documented somewhere?

Brian

On 10 May 2017, at 14:29, Schulte, Mark D <mark.d.schulte at boeing.com<mailto:mark.d.schulte at boeing.com>> wrote:

Brian,

Here were my original thoughts when I looked through this a few months ago.

1)            Update workgroup leads, close down non-active workgroup pages (http://open-services.net/workgroups/) , e.g.
a.            Embedded Systems Working group not active
b.            Performance Monitoring?
c.             Revisit the distinction between user groups and working groups, make sure pages are consistent vs. that.  Are all of the groups listed correct?
d.            Check for correct status of all groups/specs on this page.
e.            Update “Gathering industry experts” section accordingly on home page.
2)            The podcast page is pretty dated (all information is 2012 that is out there now).  Most of the info is probably still good but certainly nothing since 2012 argues against a vibrant community.
a.            Perhaps can have Rainer record his talk from IoT event and post that or at least post the slides somewhere as a community update.
3)            Pages go blank and no feedback when subscribing or unsubscribing to things.   It seems to take but you have to manually refresh.  Can this be fixed?  May be OBE now with the switch to a completely new site.
4)            Are all of these mail groups still needed?
a.            http://open-services.net/mailman/listinfo (in any event this should be prominent)
5)            I would recommend moving the Vision Statement from a link in the ‘The Latest’ Section on the homepage to a permanent link in the main section on that page.
6)            We could take our strategy proposal for accelerating OSLC standards and adoption (as this solidifies) as drafted by Martin and make a home for those ideas on our participation page
a.            http://open-services.net/participate/
7)            Perhaps we could post the photo from the IBM CE Conference (associate names and faces to people involved) and place that on the home page.
8)            Somewhere we should refer to OSLC4MBSE - http://www.omgwiki.org/OMGSysML/doku.php?id=sysml-oslc:oslc4mbse_working_group and tie that in as an OSLC working or user group, as appropriate (even though doing their work right now under the auspices of the OMG because of the SE ties)

-----Original Message-----
From: Oslc-Communications [mailto:oslc-communications-bounces at open-services.net] On Behalf Of Brian King
Sent: Friday, May 05, 2017 10:18 AM
To: oslc-communications at open-services.net<mailto:oslc-communications at open-services.net>
Subject: [Oslc-communications] Site Data Retention and Migration

Hi Comms People,

In terms of moving from the current site to a new one...

I am aware of the need to retain the site namespaces and vocabularies / shapes, and am chatting to Jim Amsden and other about this. More at:
http://open-services.net/wiki/core/Vocabulary-index/

However, I have a question about other types of data on the site. I have found these categories, but there may be more.

Please have a look through them and if you have any insights on the questions I have please let me know. In particular I am interested in what types of data (not page-by-page or post-by-post) need to be carried over to the new site, and which not. Migrating some types of data brings as yet unknown complexity to the project. For example, carrying over user profiles and forum posts will be difficult. My preference would be to start fresh and ask people to sign up again. Perhaps we could do something like just provide a read-only archive of old posts. Wiki data is probably more portable, but we could lose history and other aspects of the data.

1. Static pages
For these, we can just audit them and decide which ones we need to pull over to the new site and which can be discarded.

2. Resources
https://open-services.net/resources/
I imagine a lot of this has to stay, and needs to be surfaced up in a compelling way. Some have special needs, e.g. tutorials with special navigation … I will try to work through these section by section and build that into the requirements of the new platform.

3. Wiki pages
http://open-services.net/wiki/
Do we need to migrate wiki pages?

4. Forum Posts
http://open-services.net/forums/
Do we need to migrate forum posts?

5. User profiles (part of forum system)
E.g. http://open-services.net/forums/member/85/
Do we need to carry these over or can we start fresh?
Carry over might be impossible unless we use the same auth and forums system, which is unlikely.

6. News
http://open-services.net/blog/
Do we need to carry these over or can we start fresh?

7. Mixed Content
Some pages look like they have mixed content, meaning some static and some dynamic data, e.g. workgroup pages http://open-services.net/workgroups/communications/
This seems to be a feature of the software and while nice we may have to sacrifice it with the new platform, at least at the start.

Thanks,
Brian

_______________________________________________
Oslc-Communications mailing list
Oslc-Communications at open-services.net<mailto:Oslc-Communications at open-services.net>
http://open-services.net/mailman/listinfo/oslc-communications_open-services.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-communications_open-services.net/attachments/20170510/0747cc92/attachment-0003.html>