lter / im-manual Goto Github PK

In the paragraph under the Content heading, fix these typos:

• it's should be its
• acheive should be achieve
• thse should be these

Document and share process to add events on web site or LTERHub

Biblio, personnel, etc.

hello world

Should there be a place here for metadata recommendations such as https://ediorg.github.io/data-package-best-practices/? i was looking at https://lter.github.io/im-manual/new-to-im and https://lter.github.io/im-manual/eml,, but I don't know where most people would be looking for it.

The site-personnel page states that Row 1 lists the common-language descriptions of each field. However, it actually starts on row 2.

Can the name fields accept hyphenated names? What about other special characters? What about things like apostrophes vs the fancy apostrophe Word uses (straight quotes vs smart quotes)?

Are initials allowed (most commonly used for middle names)? If so, Should a period follow the initial?

The Active User column does not appear to contain logins as indicated in the documentation, but rather a boolean value, e.g., TRUE.

What are columns S through AC?

Is Primary (Affiliation) just for that LTER site or across all LTER sites?

In the spreadsheet, should Contact-Site ID be renamed to Site-Contact ID to match the documentation? Also, that is the only column name not in bold.

If adding a new participant with two roles, are both rows adjacent or does the second role go in the "adding roles" section after the blank row.

• What about historical documents from the old IMC website? Current link to document archive indicates ‘historical’, but that is where current website design and IM guidelines are located. They should be featured better in outline.
• Link to hub IM page, but no conversations there yet - should we set a better example?
• @Marty I would also suggest making links to other pages (like the creating the case thing) open in a new tab
• The suggest an event item might be a link to events in the Hub
• Suggestions:
  • Menu
  • Link back to home page
  • Update date
  • NTL is also a DEIMS site
  • Resources
  • General IM guidelines
  • Website Guidelines not linked

Renee’s suggestions:

• each page needs a link back to the home page and/or consider a table of contents on the side bar (maybe consider using a different theme like just the docs or something)
• consider table of contents also for each page
• last updated doesn't track with date actually last updated?
• "suggest edits" should either link to new page or link to page with instructions that includes a link to how to submit an issue
• deims - reframe to drupal. ntl, arc, and mcm are moving away from drupal
• website section should have sections or link-outs for biblio, data catalogs, personnel, etc...
• images would be welcomed... these pages are very text heavy
• should have resources page that links to specific things within the GDrive
• links to other sites should open in a new tab/window

Suggest edits should link to a page that describes how to use the Issue tracker before linking to the tracker.

Mentioned during the October water cooler was this resource that BLE built to easily peruse the QUDT catalogue of units. Someone asked if it would be possible to add the link to that resource to the IM website. Would this manual be a good place to catalogue helpful resources, such as this one?

On the publications page, we could add a section on how to discover publications that cite an LTER site's data. I don't know what the best way to do this is. Here's what BLE has documented, though we don't actively follow these ideas:

https://github.com/BLE-LTER/ble-handbook/blob/main/handbook.md#data-citations

i.e., send a file.

what format?

that means that we do a mass replacement, not an incremental update. That puts the burden of eliminating duplicates (lots of them) on the LNO.