Closed kelslundberg closed 9 years ago
Okay! I have a first draft of the data definition here. So I think we can start on the format?
Let's get this to display just like it does in Silva. And then Jake can make adjustments if needed?
Here's a test job post in Silva: https://editor.its.bethel.edu/silva/www/employment/openings/postings/test/edit/tab_preview
I also have some instructions here in the additional info column: https://docs.google.com/a/bethel.edu/spreadsheet/ccc?key=0AvCfERcmdTwpdHdzSXBnaGlDdEI0bXI0OVMzMG9ldkE#gid=15
I don't know if we need the robust metadata for this or not...my inclination is just to use the basic. Thoughts?
I just noticed that the Apply Now link for job postings goes to three different places:
Sodexo application Faculty application Staff application
I don't know exactly how it makes this determination on the back end. Maybe the Questions field since that's the only field that calls out sodexo specifically?
Its a little weird. First it checks the question field for Sodexo, and then it checks the "subject" in silva, which would either be staff or faculty.
Here is a quick creation:
https://cms.bethel.edu/entity/open.act?id=1ae3dfcf8c58651313b6fe6bc609bbd1&type=page&
Let me know what to modify.
@c-schwarze, lets start with this job posting at a template. We are going to start exactly the same with just a few modifications:
In Silva, we don't have labels display for some of these fields because it's either a little redundant or the field labels use HR terms that most people don't care much about...
https://editor.its.bethel.edu/silva/www/employment/openings/postings/test/edit/tab_preview
How do we want to handle this in Cascade if they're all in the same table together?
Should the 'Closing date' be 'Posting date'?
Updated the format. https://cms.bethel.edu/entity/open.act?id=1ae3dfcf8c58651313b6fe6bc609bbd1&type=page
The table is kind of goofy in my opinion. Do we want it to have 2 columns? Or remove the table and just list them?
@hamtim can you look at this one? I'd say try two columns.
let's to 2 columns with labels from the submission form.
Timothy Hammer Strategist Web & Creative Services
Bethel University 3900 Bethel Drive St. Paul, MN 55112 o: 651.638.6784 c: 515.971.5659
On Tue, Oct 21, 2014 at 1:06 PM, Eric Jameson notifications@github.com wrote:
@hamtim https://github.com/hamtim can you look at this one? I'd say try two columns.
— Reply to this email directly or view it on GitHub https://github.com/betheluniversity/cascade/issues/316#issuecomment-59971031 .
Updated to 2 columns and reduced the size of the button
I think this looks better. @e-jameson what do you think?
The link isn't loading properly for me. There is a velocity error somewhere @c-schwarze ?
Links within cascade pages don't normally work. Works fine once you publish: https://staging.bethel.edu/_testing/caleb-test-folder/job-posting
Yeah I think that looks good.
I believe a job posting could have both a Posting Date and a Closing Date. In Silva, the Posting Date is simply the day it was published (I believe). And a Closing Date would be the date the posting is scheduled to come down.
Is that right @hamtim?
yeo.
yes, yeo.
Timothy Hammer Strategist Web & Creative Services
Bethel University 3900 Bethel Drive St. Paul, MN 55112 o: 651.638.6784 c: 515.971.5659
On Wed, Oct 22, 2014 at 8:09 AM, kelslundberg notifications@github.com wrote:
I believe a job posting could have both a Posting Date and a Closing Date. In Silva, the Posting Date is simply the day it was published (I believe). And a Closing Date would be the date the posting is scheduled to come down.
Is that right @hamtim https://github.com/hamtim?
— Reply to this email directly or view it on GitHub https://github.com/betheluniversity/cascade/issues/316#issuecomment-60081524 .
Okay! I made some modifications to this in order to accommodate what we talked about this morning.
Here's what I did:
Created a metadata set for Job Postings. This has: Title Description Start date (can this display on the page as Posting date) End date (can this display on the page as Closing date) School
Added a data definition field for Staff application job type. This will point to different pages with different wufoo forms. So we'll need to update the format for this once the site is built out in Cascade.
Removed closing date from the data definition since we'll be using End Date.
Removed school from the data definition since it's now in the metadata.
Job postings now work for these changes.
Example:
https://cms.bethel.edu/entity/open.act?id=345755f58c58651337aebe3f71b8cffb&type=page&
Any thoughts @hamtim
Updates needed:
Example: Position status: Full-Time, Exempt/Salaried
Example: Photography | Department of Art
We'll have pages in the site for Staff, Faculty, and Sodexo apps (not built in Cascade yet).
If people select Other for their application type, they will see the Application URL field and can add a url for where they'd like the Apply button to go. Can we get this functionality working now or would you like to wait until we have the apps for the other options in Cascade?
ugh - Github turned my numbers into strange lists
There are 4 items to address:
Status Teaching load Area of focus Application type/application url
Sorry for the confusion!
When I was chatting with Tim it sounded like we still wanted to classify a posting with a "Other" URL as either Faculty or Staff. Do we want to have that option available for all application types?
This is all ready for testing.
Looking good!
A few things:
Can we remove the "or full time equivalency" from the Hours per week label?
Can we lowercase the R in required so that it's "Resume required"?
It looks like Teaching load, Tenure track, and Benefits eligible are missing from the table:
https://cms.bethel.edu/entity/open.act?id=345755f58c58651337aebe3f71b8cffb&type=page
These are all fixed. Let me know if any of the table labels should be updated.
I have pages built for the staff and faculty applications.
They're not live yet, but the urls will be:
https://www.bethel.edu/employment/apply/staff https://www.bethel.edu/employment/apply/faculty
I don't know what Sodexo jobs link to...can we find that somewhere in the code for job postings in Silva?
Yeah here you go:
New test. It's getting there!
https://cms.bethel.edu/entity/open.act?id=58893d4a8c5865137974aa183b6ad8be&type=page
Looks like we're missing:
Months per year (it can go above Hours per week)
I see supervisor showing up below on the page along with responsibilities/education/etc. Do we want that in the table? Thoughts on that @hamtim?
I also created a page for sodexo-apply in Cascade. So that can get linked up application-type.
looks great, guys.
I guess supervisor can go in the box. It's tabular info.
-t
Timothy Hammer Strategist Web & Creative Services
Bethel University 3900 Bethel Drive St. Paul, MN 55112 o: 651.638.6784 c: 515.971.5659
On Tue, Oct 28, 2014 at 3:58 PM, kelslundberg notifications@github.com wrote:
New test. It's getting there!
https://cms.bethel.edu/entity/open.act?id=58893d4a8c5865137974aa183b6ad8be&type=page
Looks like we're missing:
Months per year (it can go above Hours per week)
I see supervisor showing up below on the page along with responsibilities/education/etc. Do we want that in the table? Thoughts on that @hamtim https://github.com/hamtim?
I also created a page for sodexo-apply in Cascade. So that can get linked up application-type.
— Reply to this email directly or view it on GitHub https://github.com/betheluniversity/cascade/issues/316#issuecomment-60830375 .
@e-jameson I think you asked to confirm, and I'm confirming, we want to have the "custom application URL" or whatever we're calling it be available for faculty and staff job types.
I fixed Months / Year and moved Supervisor to the table. All we need is the content at the bottom of the page, which @kelslundberg was going to get. Seeing as how that is static content I'd say these pages are ready for migration and testing.
Here's the first real job posting loaded into Cascade:
https://cms.bethel.edu/entity/open.act?id=580aadd48c5865137974aa18c94e3797&type=page
Please take a look and note if you see any issues!
@e-jameson - here is the content to add to the bottom of the page:
Bethel University is a leader in Christ-centered higher education with approximately 6,300 students from 48 states and 32 countries enrolled in undergraduate, graduate, seminary, and adult education programs. Based in St. Paul, Minnesota, with an additional seminary location in San Diego, California, and a satellite location in Bloomington, Minnesota, Bethel offers bachelor's and advanced degrees in nearly 100 fields. Educationally excellent classroom-based and online programs equip graduates to make exceptional contributions in life-long service to God and the world.
Bethel employs qualified individuals regardless of race, color, national or ethnic origin, age, gender, or disability. Individuals must be able to perform the essential functions of the position with or without reasonable accommodations.
I added the words.
Looks like some extra text shows up for FLSA status if it's not populated....
https://cms.bethel.edu/entity/open.act?id=580ac5448c5865137974aa18d937ab22&type=page
Can we remove that?
A few more things I'm just noticing now:
https://cms.bethel.edu/entity/open.act?id=580acdf88c5865137974aa182f3b9eb2&type=page
Can we have the second word of every heading be capitalized? Job Summary, Required Experience, etc..
Also, looks like the Additional Information heading shows up even if info is not there. Can we have that hide if not populated?
I moved Supervisor so that it's above the resume field in the data def. Can we have it display there in the format as well?
https://cms.bethel.edu/entity/open.act?id=580ac73b8c5865137974aa1805fa41de&type=page&
Thanks so much!!
I loaded a couple more and am seeing this error:
https://cms.bethel.edu/entity/open.act?id=580ab6ec8c5865137974aa187a60de11&type=page
https://cms.bethel.edu/entity/open.act?id=580acc318c5865137974aa1899a535a6&type=page&
It's only on these two most recent ones. The others seem fine.
I believe all these issues / requests have been taken care of.
What can be required:
Title Description Start date Job type Location Application type Job summary Questions
Want me do to do this?
It looks like there's an extra space before the comma that separates position status and flsa status:
https://cms.bethel.edu/entity/open.act?id=580ab6ec8c5865137974aa187a60de11&type=page&
Position number should also be required.
-tim
Timothy Hammer Strategist Web & Creative Services
Bethel University 3900 Bethel Drive St. Paul, Minnesota 55112 o: 651.638.6784 c: 515.971.5659
On Nov 2, 2014, at 4:39 PM, kelslundberg notifications@github.com wrote:
What can be required:
Title Description Start date Job type Location Application type Job summary Questions
Want me do to do this?
— Reply to this email directly or view it on GitHub https://github.com/betheluniversity/cascade/issues/316#issuecomment-61427350 .
Why are you people emailing on Sunday?
Not all jobs have position numbers in Silva right now :) So we can't make it required just yet.
On Sun, Nov 2, 2014 at 5:42 PM, Eric Jameson notifications@github.com wrote:
Why are you people emailing on Sunday?
— Reply to this email directly or view it on GitHub https://github.com/betheluniversity/cascade/issues/316#issuecomment-61429669 .
I will follow up with those posting jobs. As of today (since we launched the new applications), every job needs a number.
-tim
Timothy Hammer Strategist Web & Creative Services
Bethel University 3900 Bethel Drive St. Paul, MN 55112 o: 651.638.6784 c: 515.971.5659
On Mon, Nov 3, 2014 at 9:13 AM, kelslundberg notifications@github.com wrote:
Not all jobs have position numbers in Silva right now :) So we can't make it required just yet.
On Sun, Nov 2, 2014 at 5:42 PM, Eric Jameson notifications@github.com wrote:
Why are you people emailing on Sunday?
— Reply to this email directly or view it on GitHub < https://github.com/betheluniversity/cascade/issues/316#issuecomment-61429669>
.
— Reply to this email directly or view it on GitHub https://github.com/betheluniversity/cascade/issues/316#issuecomment-61491612 .
Sure go ahead and make then required @kelslundberg. I'll update the format accordingly.
Can I wait to make it required until we're done migrating? So that way we can keep the migration process going. I'll post all jobs here that don't have a number.
On Mon, Nov 3, 2014 at 9:57 AM, Eric Jameson notifications@github.com wrote:
Sure go ahead and make then required @kelslundberg https://github.com/kelslundberg. I'll update the format accordingly.
— Reply to this email directly or view it on GitHub https://github.com/betheluniversity/cascade/issues/316#issuecomment-61499223 .
Works for me.
sure.
I did email the posters this morning and asked them to update.
Timothy Hammer Strategist Web & Creative Services
Bethel University 3900 Bethel Drive St. Paul, MN 55112 o: 651.638.6784 c: 515.971.5659
On Mon, Nov 3, 2014 at 10:31 AM, Eric Jameson notifications@github.com wrote:
Works for me.
— Reply to this email directly or view it on GitHub https://github.com/betheluniversity/cascade/issues/316#issuecomment-61504894 .
I'm guessing they'll just be updating job numbers? We're part way through migration and we'll finish today.
We're going to get employment moved over. So that means we need job postings in Cascade.
I'll build a data definition. I'll pass it along when it's done.