We should provide e-mail confirmation for account users when they do a submission.

    <div class="field">
      <%= f.label :category %><br>
      <%= f.collection_select :category_id, Edition.current.categories, :id, :full_title, prompt: true %>
    </div>

print NOTHING

Work edit form is quite different from the new form in that you already have selected stuff which might need to be changed etc.

As of now, this requires a pretty substantial refactoring otherwise it won't work.

formtastic seems to be pretty promising for complicated forms. Maybe we should investigate this and other tools to make our life easier.

[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (jquery.iframe-transport.js, line 0)

To avoid having too many authors without roles we should perhaps set a default Role, such as Music Composer.

This should be done after #35.

Comments on this issue are more than welcome.

I am trying to make the social login work with facebook, twitter etc. (related to #10 and #15) but maybe the code is a bit old the APIs have changed or whatever I am totally unable to get the proper keys myself. HEEELP!

The keys should all go in a file in config/social_keys.yml like so:

#2015-07-23 RICHARD:
# THIS IS A SAMPLE FOR social_keys.yml which is git-ignored as it should be, because it will have your keys in it.
# REMEMBER TO COPY THIS FILE TO social_keys.yml AND CHANGE THE KEYS IN THERE TO MATCH YOURS.
development:
  facebook_key: '1667484636870927'
  facebook_secret: 'I dont have a secret for this :-('

  twitter_key: "YOUR_KEY"
  twitter_secret: "YOUR_SECRET"

  github_key: "YOUR_KEY"
  github_secret: "YOUR_SECRET"

  linkedin_key: "YOUR_KEY"
  linkedin_secret: "YOUR_SECRET"

  google_key: "YOUR_KEY"
  google_secret: "YOUR_SECRET"

production:
  facebook_key: '1667484636870927'
  facebook_secret: 'I dont have a secret for this :-('

  twitter_key: "YOUR_KEY"
  twitter_secret: "YOUR_SECRET"

  github_key: "YOUR_KEY"
  github_secret: "YOUR_SECRET"

  linkedin_key: "YOUR_KEY"
  linkedin_secret: "YOUR_SECRET"

  google_key: "YOUR_KEY"
  google_secret: "YOUR_SECRET"

should be

resources : works do
   resources :works
end

Account/New Author

• First author precompiled by owner data
• telephone number
• location --> addresss, city, zip code, state/prov/region (string) , country (tendina)

Authors

• Nationality
• Role

Works

• Category ID
• [ ]

Category

• Category
• Short description
• Long description

directories should be uploaded as such, or perhaps zipped and then uploaded?

not drop, maybe there is a missed js callback

Maybe checkout the one that is used in WeTransfer.

When you follow the path of creating a new author the app crashes. Showstopper.

add file_field and test that it can upload files into the proper directory

contexts; music, text, video, performance, etc.
roles: author, etc.

Note: this implementation is too complicated (the relationship between them is many-to-many. Let's do a simpler one right now.

Is a part of MailChimp that we use for mailing list. It could simplify the mail workaround.

there is not possibility to add other files. There should be.

There are some death CSS pointer like:

class='work_title'

find a way to search it, like with a validator

At the end of the day, it is better that:

1. the relationship between works, authors and roles is asymmetrical (instead of a symmetrical one that implies a three--way many-to-many relationship with the AuthorWorkRole table, which is almost unmanageable
2. true, this becomes a deeply nested architecture which is frowned upon in the rails world, but I think things are anyway clearer this way.

Thus: at the end of #34, the next step is to nest roles into authors. Therefore, the user journey will become:

1. Account adds a new work
2. Account selects one or more authors along with the work created (should be mandatory, but how is it to be done, since these relationships are many-to-many?)
3. by selecting each Author, Account has to decide upon the role and/or roles (this should be mandatory too, if we can figure out how to do it mandatory)

I'm not able to do it.

check it out:

capybara is used to create automated tests of full user interaction with the application.

user -> has_many :works. This should use the whole devise shabang: will try to use this

We need to make a capybara test upon failing sign up procedures. There are no flash notices, thus it is difficult to understand what is going on. Furthermore: it's a bit funny. Signing in requires an e-mail but then the e-mail is not reported in the inner form.

As foreseen. author => many-to-many => works

Hard links will work only on a controlled "all local" environment. While testing on some IaaS cloud, for example, consistency of file systems is not guaranteed. Thus, the hard links created during testing related to SubmittedFiles tests may fail. Better use copy or symbolic linking instead.

I'll reactivate it when it works.

app/views/accounts/shared/_links.html.erb

Author was successfully created without BIO ENG.

now the button name is Select Authors

Author shouldn't be younger of 18 years old

A login interface to grant personal access on submission form and file upload.
A ready to shot option could be:
https://github.com/mohitjain/social-login-in-rails.git

Using the ActiveAdmin gem.

eh… 

The checkbox values are not properly set in the editing form (which references app/view/work/_select_roles.html.erb).

The listing of works is not properly agenced. Also, we should think about who exactly should be able to see this page (it should not be in the common routing mechanism).

We have some reports (@micsuperfly, #47) that the password reset has some problems (though the problems themselves are not specified).

We should:

1. create a capybara features test to check the password reset procedure thoroughly
2. fix the problems :-)

The editions table should contain the following fields:

• :year, :null =› false, :uniq =› true
• :title, :null =› false
• :introduction_en,
• :introduction_it

A has_many/belongs_to' relationship should be added with the Work object

This should have a default class method which reads a config/editions.yml configuration and caches the default edition for every year

after send me reset password instructions nothing

Encoding::UndefinedConversionError in WorksController#upload_file