openaim / openrfa-website Goto Github PK

Current COBie Attribute and COBie Mapping lists are specific to COBie v2.4. Need versioning and version labeling strategy as COBie v3 is not far away. My hunch is separate tables would be best rather than versioning per attribute in one table.

• At a minimum in the near term, the COBie Attribute and COBie Mapping pages need to update titles/labels to include “v2.4”

http://openrfa.org/documentation/life-cycle-parameter

When mapping COBie attributes to Revit parameters, there needs to be a way to map to built-in Revit parameters such as Manufacturer.

• Is it possible to obtain the GUID of built-in parameters? Maybe with RevitLookup?

• Is there a fully itemized list of Revit system parameters and OOTB family parameters somewhere?

http://openrfa.org/documentation/regional-multi-language-support

• Test RESTws: https://www.drupal.org/project/restws
• Test RESTful module: https://www.drupal.org/project/restful
• Test Services module: https://www.drupal.org/project/services

In order to give people high level view of the types of entities and relationships in Revit.

Needs review and comment.
Revit Data Conceptual Map.pptx

From gitme iOS

When saving a new revision to a parameter, an email is sent notifying the author that their parameter has been "approved" as if it is a new parameter.

• COBie to IFC mapping data already exists and is part of the COBie standard, so fully documented, vetted, and standardized.

• Mapping is transitive, so if somebody maps a SharedParameter to an IFC property, and we already have the COBie to IFC property mappings then the COBie to SharedParameter is automatic. Taken to the extreme, linked data might provide the most robust (but complicated) approach.

Create a content type for COBie so it can be treated as it's own table. Create relationship between two types so that they form a relationship.

To encourage more open feedback, add a "Suggest A Change" link to the bottom of all OpenRFA.org pages.

• http://openrfa.org/about/how-it-works
• http://openrfa.org/documentation/life-cycle-parameter

Start with the simplest example of a Revit schedule which implements OpenRFA shared parameters. Use as proof of concept to work out:

• where/how to present on website
• how/if to store on github
• one file per schedule versus one file for collection of related schedules
• Revit versions? Last 3? 2019, 2018, 2017?
• consensus building process (one approach would be a call for submission of examples used in practice, with an emphasis on real use cases instead of idealized versions); compare against NCS standard schedules
• template for schedule container file (remove all families, purge repeatedly until empty to minimize cruft and file size)
• whether or not to "unit test" with a family loaded with shared parameters to show the schedule in action
• user documentation on how to use

The message sent to Zulip says that the parameter was approved when the parameter was already approved, it was simply edited. We need more specific messages sent to Zulip.

Incorporate review workflow to website changes so deltas are obvious to all authors.

The body of a forum post is cutoff horizontally when viewed on mobile. Tested on Samsung Galaxy S9+.

• http://openrfa.org/documentation/filtering-definitions-file

• http://openrfa.org/documentation/download-filtered-definitions-file

• http://openrfa.org/documentation/parameter-sets

• https://zulipchat.com/integrations/doc/github

• https://zulipchat.com/integrations/doc/github_detail

• The COBie Mapping Table should move COBie Attributes to the left column and Revit Shared Parameters to right column.

• The COBie Mapping Table also needs to be sorted by COBie Attribute and Column to illustrate all COBie Attributes that don't yet have a Revit Shared Parameter mapped.

• The COBie Mapping Table filtering options and design should also match filtering on COBie Attribute page.

https://github.com/OpenAIM/OpenRFA-Website/community

• Description
• Topics
• Readme
• Code of conduct
• Contribution guidelines
• License
• Issue templates
• Pull request template
• Changelog
• .gitignore
• Webhook to Zulip
• FOSSA integration

• http://openrfa.org/documentation/data-types

• http://openrfa.org/documentation/naming-conventions

One option: https://www.drupal.org/project/eu_cookie_compliance

Pretty slick that it can use geoip to only display notifications for visitors from EU countries.

https://meta.discourse.org/t/troubleshooting-email-on-a-new-discourse-install/16326

Integrate Zulip login with OpenRFA login.

Autonaming will use this module: https://www.drupal.org/project/hierarchical_select

Per discussion with Andrew Duncan at Arup, this GitHub issue will kickoff the open discussion on OpenRFA vision and framework in order to find common ground for mutually beneficial collaboration.

Andrew, give us a little time to pull together our content and we'll post here to get the conversation rolling.

Unable to see the php you used to implement the MD include...or I'm doing something wrong.

• Move documentation from Drupal basic pages to Github Wikis.

• Link all menu items on Drupal to Github Wiki pages

• Create some sort of redirect to ensure external links currently linking to OpenRFA.org are redirected appropriately.

• The breadcrumb path on any COBie Sheet views should link back to /cobie
• All COBie attribute nodes should show a breadcrumb linked to /cobie

Use the topic (GUID) from Zulip #DataDefinitions to match the GUID on Drupal and display all messages related to the GUID.

https://www.drupal.org/project/og

Issue placeholder for idea of forking Jeremy Tammik's excellent open source RevitLookup tool.

Should use entity_reference for data definition, COBie attribute, and custom IFC property

Ensure that we have a "moderator" role and permissions are restricted as required.

This issue will collect issues/ideas for the COBie Attribute implementation for initial discussion and then create separate more specific issues as necessary for each actionable task if there is concurrence, or create a checklist here, whichever seems most appropriate. Attempted to sort by importance.

Overall an extremely good MVP!

COBie page

• Need column header for first column: “Attribute Name” or “Name”
• Order the Sheet filter list to match COBie standard: Facility, Floor, Space, etc

COBie Mapping page

• #32 Need to find a way to address existing built-in Revit parameters such as Manufacturer. Is it possible to obtain the GUID of built-in parameters? Is there a fully itemized list somewhere?
• #33 Add COBie to IFC mapping
  • COBie to IFC mapping data already exists and is part of the standard, so fully vetted and standardized.
  • Mapping is transitive, so if somebody maps a SharedParameter to an IFC property, and we already have the COBie to IFC property mappings then the COBie to SharedParameter is automatic. Taken to the extreme, linked data might provide the most robust (but complicated) approach.
• Add COBie Attribute to Filter options
• Would be useful if spreadsheet tab name in COBie Attribute column (ie Component) were hyperlinked to trigger a filter by that tab
• #35 Mapping table should include all COBie Attributes and highlight missing Revit Shared Parameters

Applies to both pages:

• #36 Current lists are specific to COBie v2.4. Need versioning strategy as COBie v3 is not far away. My hunch is separate tables would be best rather than versioning per attribute.
  • #36 Need to update titles/labels to include “v2.4”

• Would like to see way to increase default list display length, up to a very long list, including “All” even if that is time consuming it would be helpful to see all at once. It’s <300 so not too taxing.
• Column headers should be sortable (true for SP pages too)
  • Sortable column headers for COBie Mappings page
  • Sortable column headers for SP pages

Applies to other:

• Recommend including a link to the COBie Attributes page in the main menu within Shared Parameters below Parameter Sets (or something better?).

See great example here:
https://github.com/3drepo/3drepo.io/issues/new

• http://openrfa.org/about

• http://openrfa.org/about/team (don't forget to add Van!)

• http://openrfa.org/about/how-it-works

• http://openrfa.org/faq-page

https://www.drupal.org/node/803746

Also would be good to figure out how to create forks for replicating the site for different collaborative standards development purposes.

Minimize friction to account creation. LinkedIn authentication particularly interesting due to professional networking emphasis. Other authentication methods are fine as well, whatever is easiest to implement with an existing Drupal module.

@jmerlan Can you add the images and native editable files to:
https://github.com/OpenSourceAssetInformation/OpenRFA/tree/master/WebsiteContent/Documentation/Assets

There’s the website sm and medium sized favicon for OpenRFA, not sure if there are others. Would like to get an icon together for OSAI

For OpenRFA SSO, is there a way to merge or associate existing accounts to github/linkedin logins? Also between github and linkedin logins so you didn't have to have two accounts or remember which one you logged in with originally?