at top of try something random box (or ??) - add content from Meta/Global
I had to rewrite the header model to fit this in
PLEASE TEST THE LAYOUT AT http://arctos-test.tacc.utexas.edu/
Default:

Hover:

I like how you make it a small box as default, then expand with the mouse hover. And being able to have hyperlinks to events, etc. is key. Nicely done.
Yes, looks great. Will this be Twitter feed?
On Tue, Nov 14, 2017 at 2:32 PM, Angela Linn notifications@github.com
wrote:
I like how you make it a small box as default, then expand with the mouse
hover. And being able to have hyperlinks to events, etc. is key. Nicely
done.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/1327#issuecomment-344405872,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOH0hITWNM_HqgSkRJBMxE1j-w51Pn9rks5s2gb_gaJpZM4QcehI
.
Thanks. No, it's not twitter, it's a new field in manage/meta/global.

I don't think it should be twitter either - I'm not sure who our twitter audience is, but it doesn't include me and probably many other Arctos users. The "newsfeed" is targeted at active Arctos users. I don't think there's reason to assume overlap between those groups.
I agree. I'm not on Twitter either. However, it was proposed as a way that
the AWG could have access to post news issues without having to modify the
web portal directly.
On Tue, Nov 14, 2017 at 4:09 PM, dustymc notifications@github.com wrote:
Thanks. No, it's not twitter, it's a new field in manage/meta/global.
[image: screen shot 2017-11-14 at 3 04 51 pm]
https://user-images.githubusercontent.com/5720791/32809806-314f945e-c94d-11e7-850d-2fb5d6e05b96.pngI don't think it should be twitter either - I'm not sure who our twitter
audience is, but it doesn't include me and probably many other Arctos
users. The "newsfeed" is targeted at active Arctos users. I don't think
there's reason to assume overlap between those groups.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/1327#issuecomment-344430843,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOH0hJnCjc8ZIwvq5wpCz8NkZA9RzAy6ks5s2h2ZgaJpZM4QcehI
.
This doesn't require CODE being modified, only a form entry, and everyone on the AWG likely already has access to that form. (I think it's manage_global rights.) I'm not sure if that's what you're saying or not, and I'm always up for better ideas.
Do we have documentation yet on how to use the form? Would be a good thing
to disseminate.
On Tue, Nov 14, 2017 at 4:20 PM, dustymc notifications@github.com wrote:
This doesn't require CODE being modified, only a form entry, and everyone
on the AWG likely already has access to that form. (I think it's
manage_global rights.) I'm not sure if that's what you're saying or not,
and I'm always up for better ideas.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/1327#issuecomment-344433278,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOH0hHKmUGwoGkoaSQGreK_FN_GSqz8bks5s2iBOgaJpZM4QcehI
.
Want to write that and I'll answer questions? I'm not sure what needs documenting??
What needs documenting:
"everyone on the AWG likely already has access to that form. (I think it's manage_global rights.)"
I don't know anything about managing global rights or forms that let me make changes to the website - I didn't even know I had access to do such things. Maybe more than documentation is required. I feel like I need some sort of training to be an AWG member....
I feel the same as Teresa. I guess we need to put together some guidelines.
On Nov 15, 2017 1:10 PM, "Teresa Mayfield" notifications@github.com wrote:
What needs documenting:
"everyone on the AWG likely already has access to that form. (I think it's
manage_global rights.)"
I don't know anything about managing global rights or forms that let me
make changes to the website - I didn't even know I had access to do such
things. Maybe more than documentation is required. I feel like I need some
sort of training to be an AWG member....—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/1327#issuecomment-344713534,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOH0hImdNkSv-_-3S5pju2MB57BLvYW_ks5s20UegaJpZM4QcehI
.
No disagreement for any of that, and i'm happy to do whatever, I just don't think I'm the best person to write docs - I don't generally need documentation to understand my code, and so I'm never quite sure what about the code might need documented.
"manage_global" (actually "global_admin") is a role.

It works like any other role, and can be accessed from....

or from editAgent.

then
"Def"

provides a CRUD (https://en.wikipedia.org/wiki/CRUD) definition.
In addition to table-level access control, roles provide or restrict access to forms. You can see that here...

or set it here


controls
Under definition of the role, then, we need to add "forms permissions" with
the following added and defined. Also, we need to add documentation to
Github how to actually edit these forms and manage credentials etc. Who is
currently doing these things who can help with this documentation?
controls
On Wed, Nov 15, 2017 at 1:38 PM, dustymc notifications@github.com wrote:
No disagreement for any of that, and i'm happy to do whatever, I just
don't think I'm the best person to write docs - I don't generally need
documentation to understand my code, and so I'm never quite sure what about
the code might need documented."manage_global" (actually "global_admin") is a role.
[image: screen shot 2017-11-15 at 12 27 28 pm]
https://user-images.githubusercontent.com/5720791/32858457-6941051a-ca00-11e7-972a-261fac4b5dfc.pngIt works like any other role, and can be accessed from....
[image: screen shot 2017-11-15 at 12 28 11 pm]
https://user-images.githubusercontent.com/5720791/32858498-898eabd8-ca00-11e7-8347-f9bb8f339895.pngor from editAgent.
[image: screen shot 2017-11-15 at 12 29 06 pm]
https://user-images.githubusercontent.com/5720791/32858523-9b4c3426-ca00-11e7-8be3-8bdf765b37b4.pngthen
"Def"
[image: screen shot 2017-11-15 at 12 29 37 pm]
https://user-images.githubusercontent.com/5720791/32858537-aea1aff6-ca00-11e7-8529-06ccfc6208ca.pngprovides a CRUD (https://en.wikipedia.org/wiki/CRUD) definition.
In addition to table-level access control, roles provide or restrict
access to forms. You can see that here...[image: screen shot 2017-11-15 at 12 31 21 pm]
https://user-images.githubusercontent.com/5720791/32858634-f8fdda7a-ca00-11e7-8710-7bed920c6b24.pngor set it here
[image: screen shot 2017-11-15 at 12 32 06 pm]
https://user-images.githubusercontent.com/5720791/32858648-0635920a-ca01-11e7-82c9-ee61fac7fa5f.png[image: screen shot 2017-11-15 at 12 20 52 pm]
https://user-images.githubusercontent.com/5720791/32858172-72765df2-c9ff-11e7-96fc-2da14824fd12.pngcontrols
- newsfeed banner
- Google Enterprise credentials
- Google Analytics credentials
- EZID (our source of DOIs) credentials
- GenBank credentials
- Who gets various emails
- IPs which are immune to blacklisting
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/1327#issuecomment-344721062,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOH0hAKXEkvwWwnY-Kg-qNO-igWpq0tmks5s20vggaJpZM4QcehI
.
I am not sure what you're talking about.
The tool is done+in production. Seems there may still be documentation issues that need resolved so I'll temporarily leave this open.
There should be some guidelines on content too-- this is NEWS that will be
on the public front page of Arctos for all collections, right? (GLOBAL
management)
simply and nicely done, Dusty!
On Fri, Nov 17, 2017 at 7:22 AM, dustymc notifications@github.com wrote:
The tool is done+in production. Seems there may still be documentation
issues that need resolved so I'll temporarily leave this open.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/1327#issuecomment-345273104,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACZ_0ZPmdIMW7PJwwj62ThDW-h_5djUqks5s3aTQgaJpZM4QcehI
.
It is on ALL pages for ALL collections.
Thanks!
If I understand the status of this issue correctly I should be seeing the newsfeed banner on arctos.database.museum, yes? That isn't what I'm seeing. If I am not logged in nothing is changed from pre-newsfeed. If I am logged in there is not only not a newsfeed but the "try something random" section is also gone. Both logged in and not logged in our institutional header images don't show up like they used to on catalog record pages... I was looking at this in Chrome and Firefox
I don't think there's any content in the newsfeed yet.
the "try something random" section is also gone.
Did you turn it off? My Stuff (https://arctos.database.museum/myArctos.cfm), ....

I'm still seeing TSR, but I did muck with CSS so it's possible yours is hiding or something. Screenshot and resolution details, please.
institutional header images don't show up
Woops! I'll patch that back in ASAP.
Oops, yep, I had turned off TSR. And thanks for explaining that if there's no content then no content will show up... derrr!
I guess my next question is that when I view my own permissions I have the global_admin role assigned, but under Manage Data-->Metadata I only see Encumbrances and Manage Collection, nothing about Global Settings. Should I?
Ah - it seems to also require manage_codetables

I'm ALWAYS up for guidance regarding permissions - maybe everyone on the AWG should have code table access, or that form should be more open, or whatever.
Howdy,
Liking the newsfeed but as Erika pointed out "Both logged in and not logged in, our institutional header images don't show up like they used to on catalog record pages"
i tried on Chrome and Firefox as well as for different collections (MSB:Herp, MSB:Mamm)
the HEADER_COLOR works fine but HEADER_IMAGE is not happening. Also missing is
COLLECTION_URL | COLLECTION_LINK_TEXT
INSTITUTION_URL | INSTITUTION_LINK_TEXT
The collection header switcher-inner should be switching now.
Sorry, just chiming in now. I like how the news banner expands and can link out, but the addition of the banner has screwed up the placement of the logo relative to the text "Collaborative Collection Management Solution" - can those be lined up better? Also, who is going to be responsible for news announcements (our Communications officer?) and what are the guidelines for announcements? Seems like we need to have some guidelines before we put this into production. If we have a news feed, then we need to keep it active and dynamic.
screwed up the placement of the logo
Screenshot please.
Maybe it should auto expire and vanish a certain amount of time after
posting?
On Nov 22, 2017 10:23 AM, "Carla Cicero" notifications@github.com wrote:
Sorry, just chiming in now. I like how the news banner expands and can
link out, but the addition of the banner has screwed up the placement of
the logo relative to the text "Collaborative Collection Management
Solution" - can those be lined up better? Also, who is going to be
responsible for news announcements (our Communications officer?) and what
are the guidelines for announcements? Seems like we need to have some
guidelines before we put this into production. If we have a news feed, then
we need to keep it active and dynamic.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/1327#issuecomment-346418873,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOH0hG_cJHTjK4nhi7jnw4MUgZ9RHczyks5s5FhhgaJpZM4QcehI
.

versus

Auto-expire/vanish is a good idea if that's possible. We just don't want stale news, and it takes work to keep this fresh.
Derp - thanks! Fixed and patched into prod.
Auto-expire
Yes, it's possible. When would news expire? 2 weeks?
I just updated the news item in test but it's not updating on the banner - cached?
Could we choose an expiration date (add a calendar widget)? Some news may require a shorter and known expiration - e.g., planned outages - whereas we may want to keep others posted longer.
cached
Yup.

But I just turned that off in test so it should be live now.
choose an expiration date
Good idea, I like.
choose an expiration date
Done at test, for next release.

Needs live forced-refresh preview
save now flushes cache
Hi all, I just went in to the banner page to fix the dates from "5/27 to 5/27" to "5/27 to 5/29". I like that I can now just type free text and don't have to deal with encoding the English. But it is very concerning to be making these edits on a page where there is so much other critical stuff. I don't have a cat, but if I did and he walked across my keyboard while I turned away for a sip of coffee, I could really mess up something in there while working on the banner. Any way to move the banner to its own form in PG? Maybe with separate permissions, for communications only?
Yes, but let's do it in https://github.com/ArctosDB/arctos/issues/2702
Most helpful comment
I like how you make it a small box as default, then expand with the mouse hover. And being able to have hyperlinks to events, etc. is key. Nicely done.